Urgent.News

What's breaking now, across thousands of outlets.

Tech

Nothing dead — giving every experiment a decision date

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…

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.

The 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.

Initially, 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.

The 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.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The Cheaper HMI Is Costing You More: A TCO Breakdown for Engineers

Every procurement cycle hits the same wall. The membrane switch assembly quotes at a fraction of the panel PC price. The spreadsheet says “option A.” The line engineer says “option B.” Someone in…

  • Membrane switches suffer from drift-induced quality loss over time.
  • Membrane switch panels risk obsolescence with limited supplier alternatives.
  • Panel PCs reduce changeover time by up to 67% compared to membrane switches.

GDPR Article 22's "right to an explanation" is an engineering requirement in disguise

Every time Article 22 comes up, the same argument starts. Lawyers debate what "meaningful information about the logic involved" is supposed to mean, and engineers start reaching for SHAP plots.

  • Article 22 requires explanation of automated decisions
  • Finding specific decision and inputs is challenging
  • Auditability and organization are core compliance issues

Turn a Live Q&A Transcript Into a Lesson and Recap With Python

If you run a community, a course, or even a team office hour, you probably record live Q&A sessions. Then the recording sits there. Nobody rewatches an hour of video.

  • Python script automates turning live Q&A transcripts into lessons and recaps
  • Transcript parsed into questions and answers using regex and file handling
  • Best answer identified as longest answer for lesson creation

How I Built a Real-Time Vehicle Inspection Lookup Tool for Colombia (2026)

A few months ago, a friend asked me how to check if his car had passed its mandatory technical inspection. I told him to go to the RUNT portal — but the experience was slow, confusing, and nearly…

  • Mandatory RTM inspection required for all Colombian vehicles.
  • Government data stored in RUNT database, but querying is problematic.
  • Lightweight lookup tool prevents costly fines and operational disruptions.

PyPI Package Hijack Without Repo Changes Exposes Source, Build, and Registry Trust Gaps

The Phantom Commit: How a Trusted Package Turned Hostile Without Touching GitHub When teams look at an incident like the Microsoft Agent Framework package compromise on PyPI, the first instinct is to…

  • PyPI package compromised without repo changes
  • Versions 1.26.1 and 1.26.2 contained credential-stealing code
  • Decoupling allows malicious wheels to bypass verification

More from Friday 20 November →