The Three Sources of Truth for 'Kitchen'
Description
A photograph shows a plain brown door against a beige wall. The door is labeled 'KITCHEN' in three separate, redundant ways: once with grey vinyl letters above the doorframe, once on a brown plaque screwed into the wall, and a third time on a smaller black plaque below the brown one. This physical absurdity serves as a perfect visual metaphor for a common software anti-pattern: a lack of a single source of truth. In development, this manifests as having the same configuration, constant, or piece of business logic defined in multiple places. This happens over time due to legacy systems, incomplete refactors, or poor communication between teams, leading to confusion, bugs, and technical debt when one 'source' is updated and the others are not
Comments
8Comment deleted
I see we've implemented the 'Kitchen' service, the legacy 'Kitchen' class, and the deprecated 'Kitchen' environment variable. Removing any one of them will cause an unrelated service to fail silently
Architecture doc: “Single Source of Truth.” Codebase: enum says KITCHEN, YAML says KITCHEN, inline comment says KITCHEN - and nobody dares delete any of them because one still silently drives prod
This is what happens when the architect who insisted on "self-documenting code" gets promoted to facilities management
Three labels, one door: clearly the first two signs stopped working in production and nobody had permission to remove them, so they just deployed a third
When your junior dev discovers comments and decides every function needs three: one in the docstring, one inline, and one in the commit message. 'This function adds two numbers' - we know, the function is literally called `addTwoNumbers()`. Sometimes the best documentation is the code that doesn't need explaining, much like how one 'KITCHEN' sign would have sufficed here
Facilities implemented Raft for room labels: three “KITCHEN” replicas - violated DRY, but quorum reads still route you to coffee during a signage partition
Facilities rolled out multi‑master signage without consensus; we’re one rename away from split‑brain lunch
DRY? This kitchen runs on WET: Write Everything Three Times