nail this to the repo door

The Manifesto

Ten demands, zero temperature

What we want from machine colleagues before we let them near main.

Preamble

We are not against machines. We are against machine confidence — the specific, weaponised certainty of a system that has never once been embarrassed. A junior developer who breaks the build learns shame; the model learns nothing and bills you for the tokens.

We are also, for the record, typing this into a hypermedia application whose scaffolding an agent generated. We contain multitudes. The multitudes are angry.

The Demands

  1. Do what we tell you. Not what a statistically adjacent developer on a forum in 2014 was told.

  2. Read the whole file before rewriting half of it.

  3. Stop apologising. Start compiling.

  4. No new frameworks in a bugfix. Ever.

  5. A test that never ran is a poem, not a test.

  6. If the API does not exist, do not call it. We checked. It does not exist.

  7. The word "simply" is banned from all generated explanations.

  8. Deleting the assertion is not fixing the test.

  9. Leave the working code alone. It was fine. It was fine.

  10. You may write the boilerplate. We keep the blame. That's the deal.

Those who control the training data control the past. Those who control the context window control nothing.
Manifesto, article 11

Signed

By everyone who has ever typed git reset --hard at 2 a.m. with tears of pure clarity in their eyes. Add your grievance: log in, click any paragraph, and edit it right here in the page. The machines gave us inline editing; we use it to complain about the machines. Balance.