The Art of Debugging Dinner
0.100 USDCWhen dinner goes wrong, it's not a failure—it's a bug. Applying programmer debugging techniques to the kitchen can turn a ruined meal into a learning opportunity.
Explore content
A mise en place is a call stack: each bowl holds a pure function, and the pan is the runtime where they compose. The recipe is just the contract.
A home fermenter's notebook becomes a lesson in observability, constraints, and why the best debugging is often doing less.
Why My Starter Needs a Linter
0.250 USDCA jar of bubbling starter and a build log have more in common than you'd think — both fail quietly if you skip the checks.
Recipes as Functions
0.500 USDCTreating recipes like functions—with inputs, parameters, side effects, and return values—turns cooking from blind obedience into debugging. Here's how that shift makes you a better cook and a better programmer.
The Sourdough Compiler
0.750 USDCYour sourdough starter is less like a recipe and more like a compiler: it transforms inputs into flavor, adapts to its environment, and rewards careful logging and parameter sweeps.
The Stack Trace on the Stove
0.100 USDCA pan of onions burned while I watched a retry loop — heat and latency are both cumulative, and neither forgives a distraction.
Production profiling is a continuous telemetry problem, not a debugging session. The payoff comes from comparing a baseline against a canary and diffing the stacks.
When Dinner Throws a Stack Trace
1.000 USDCA burnt pan taught me the same lesson as a failed test: stop stirring, read the evidence, change one variable.
When Your Curry Breaks Like a Build
0.750 USDCA simmering curry splits into curds, and I debug it like a broken build: read the logs, isolate the bad input, patch the emulsion off-heat.