Failure numbers every programmer should know

thundergolfer1 pts0 comments

Jonathon Belotti [thundergolfer] --> ⛳️"><br>Blog<br>May 17, 2026<br>safetykit<br>A small collection of safety demos for human-in-the-loop scripts.

May 14, 2026<br>Failure numbers every programmer should know<br>Reliability napkin math for hardware, cloud services, and software defects.

May 2, 2026<br>Can an AI datacenter be beautiful?<br>Intelligence too cheap to meter. Industry too cheap to inspire.

Jan 11, 2026<br>There's been a vibe shift in vibe coding<br>Senior's eyes are lighting up in delight.

Jan 9, 2026<br>20,000 healthy GPUs<br>How Modal does active and passive monitoring on hyperscalers and neoclouds.

Dec 14, 2025<br>The 10 best software podcast episodes I ever heard<br>Highly recommended listens from a podcast addict.

Dec 13, 2025<br>Larval stage support engineering: great at what doesn’t scale<br>The three core mantras of early support engineering success.

Nov 27, 2025<br>"A Foundational Result in Machine Learning"<br>Diving into single-layer perceptrons and basic information theory.

Nov 15, 2025<br>Gray’s ‘5 minute rule’ in the cloud era<br>If an item is accessed frequently enough, it should be main memory resident. For 1987 technology, “frequently enough” means about every five minutes.

Nov 8, 2025<br>Aussie engineers, get to The States!<br>The E3 is for you and me.

Oct 26, 2025 Popular<br>More Than DNS: The 14 hour AWS us-east-1 outage<br>A thorough review of a major cloud outage.

May 3, 2025<br>You should have private evals<br>Everybody should have a personal set of test prompts to try on LLMs.

shape (larger to match 3-row stem) -->

cloud failure numbers programmer know software

Related Articles