Nicholas Hopper

Burn-down list

A burn-down list is a file of known violations of a rule that is allowed to shrink but never to grow. Nicholas Hopper uses one to enforce a new lint rule in continuous integration from the first day, without first fixing every existing violation.

How Nicholas Hopper uses it

At APX Stream, Hopper introduced design-system rules as lint bans. Turning them on would have failed the build on every existing violation, and leaving them off until the code was clean would have let new violations in.

He listed every file that already violated a rule in an exemption file and enforced the rules everywhere else immediately. The exemption file may only shrink: removing a file from it is allowed, adding one is not. Three sweeps emptied it.

Why it suits agent-written code

An agent given a rule with no enforcement will drift from it. An agent given a failing build on hundreds of unrelated files will try to fix all of them in one unreviewable change. The burn-down list gives the agent a rule that is enforced for its own change and a bounded list to work through separately.

Related skills