Floating-point will quietly corrupt your emissions math, and 0.1 + 0.2 already warned you
Floating-point arithmetic can lead to significant errors in emissions calculations, particularly when reconciling totals. A common example is the discrepancy seen in the sum of 0.1 and 0.2, which results in 0.30000000000000004 instead of the expected 0.3. This issue becomes critical in emissions accounting, where exact figures are necessary for audits and compliance.
- ▪Floating-point errors can accumulate significantly when summing large datasets.
- ▪In emissions accounting, even small discrepancies can lead to audit failures.
- ▪The IEEE 754 standard for floating-point representation can introduce rounding errors that affect calculations.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/jeremiah_say/floating-point-will-quietly-corrupt-your-emissions-math-and-01-02-already-warned-you-g2 |
| Publication time | Sat, 23 May 2026 00:04:20 +0000 |
| Retrieval time | 2026-05-23T00:32:03.512Z |
| Last seen | 2026-05-23T00:32:03.512Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | v8Lyj60KArvO |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3923050) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Jeremiah Say Posted on May 23 Floating-point will quietly corrupt your emissions math, and 0.1 + 0.2 already warned you #javascript #programming #math #carbon Every developer has seen this: 0.1 + 0.2 // 0.30000000000000004 Enter fullscreen mode Exit fullscreen mode It's the most-shared bug in programming. You learn it, you nod, you move on — because in most code the error is so far down the decimal that nothing notices. A pixel is off by a billionth. A timer fires a nanosecond late.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
