A Field Guide to Bugs
Software bugs have existed since before modern computing, with engineers across time and systems identifying recurring patterns in how software fails. The article describes a taxonomy of common bug types, each with distinct behaviors and challenges, from reliably reproducible Bohrbugs to elusive Heisenbugs that vanish under observation. These categories reflect shared experiences in software development, illustrating the universal struggle of debugging complex systems.
- ▪The Bohrbug is a consistently reproducible bug that behaves predictably and is easily diagnosable.
- ▪Heisenbugs disappear when observed, such as during debugging, making them extremely difficult to isolate and fix.
- ▪Off-by-one errors are among the most common bugs, often causing security vulnerabilities due to incorrect loop or array bounds.
- ▪Race conditions occur only under specific, rare conditions in production and are notoriously hard to reproduce.
- ▪Deadlocks and livelocks involve resource contention between threads, with the former freezing progress and the latter consuming CPU without advancing.
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 | Stephen Diehl |
| Canonical URL | https://www.stephendiehl.com/posts/field_guide_to_bugs/ |
| Publication time | Tue, 28 Apr 2026 09:06:35 +0000 |
| Retrieval time | 2026-04-28T09:25:06.520Z |
| Last seen | 2026-04-28T09:25:06.520Z |
| 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 | -M2JB7yLBdqt |
| 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
April 19, 2026 programming humor Reading Mode A Field Guide to Bugs Software bugs predate software. Edison used the word in an 1878 letter, eighty years before the Harvard moth and sixty before the modern computer. What he named has outlasted him. Every engineer eventually assembles a private taxonomy of the ways things fail, and the useful fact about these private taxonomies is that they converge. Engineers who have never met, working on unrelated systems in unrelated decades, arrive at roughly the same categories. The convergence is evidence that the bugs are ontologically real, and not an artifact of the human tendency to impose pattern on noise. What follows is a partial field guide.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Stephen Diehl.
Discussion
0 commentsMore from Stephen Diehl
