{
  "id": 20836422,
  "title": "Nothing dead — giving every experiment a decision date",
  "url": "https://urgent.news/2026/11/20/nothing-dead-giving-every-experiment-a-decision-date",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-20T01:47:30.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/ilya_mozerov_867dbdd91feb/nothing-dead-giving-every-experiment-a-decision-date-4jn6"
  },
  "original_language": "en",
  "account": "A new rule aimed at preventing unnecessary accumulation of unused experiments, flags, tools, documents and code paths, has been adopted in a local development culture. The rule, called \"nothing dead,\" requires every experiment, flag, tool, document and code path either to go ahead or be retired by a specified date. Going ahead means the experiment is wired to a consumer, a check or a signal, with the evidence for that decision. Retired means the experiment is deleted along with its tests, documentation and registered boundaries.\n\nThe rule was added to two tracked files to ensure it travels with the code and does not live solely in someone's memory. In a repository that had accumulated three tracked files labeled as \"experiment,\" one of them was a read-only code-map tool that could not prove an experiment was dead or safe to remove. This illustrates the importance of making the decision to retire an experiment rather than leaving it indefinitely.\n\nInitially, the rule was just a sentence in two files, but soon it will be accompanied by an owner and a due date. A small registry will keep track of experiments, their owners, start and decision dates, and whether they have a consumer or evidence justifying their retention. If an experiment fails to pass the decision date, its status will change to amber, red, or unknown, depending on when the register cannot be read. This systematic approach ensures that dead or unnecessary experiments are retired and not left behind for future readers to decipher.\n\nThe deeper lesson behind the \"nothing dead\" rule is to recognize that stopping should be as visible and rigorously measured as starting. By implementing this rule, the development culture can better manage its experiments, flags, tools, documents and code paths, ultimately improving the overall understanding and maintainability of the system for future contributors.",
  "summary": "A system that only adds will eventually be mostly additions. That sounds obvious and is easy to forget in practice. An optional tool gets merged \"for now\"; a pilot document stays a pilot; a flag outlives the question it was meant to answer. Nobody removes it, because removing it is a decision and the original decision was never scheduled. This week a local development culture I work on adopted a…",
  "key_points": [
    "\"Nothing dead\" rule prevents accumulation of unused experiments",
    "Every experiment, flag, tool, document, and code path must go ahead or be retired by a decision date",
    "Systematic registry tracks experiments, owners, start and decision dates, and consumer status"
  ],
  "editors_take": "Mandating explicit decision dates for every experiment transforms the development process by treating the retirement of code with the same rigor and visibility as its initial implementation.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}