Designation Office
Developer Despair
84 entries
Developer Despair Sprint Names
The largest genre by a wide margin, which is either a comment on the profession or on whoever maintains this register. These are not names about a sprint's goal. They are names about the code the sprint has to touch.
The vocabulary is git, blame and time. Past Me Was an Idiot, Future Me’s Problem, Commit Archaeology. Several are things a developer has genuinely said out loud, transcribed without alteration and improved only by being printed on a board where management can see them.
- Issue when
- The sprint is being spent inside a subsystem nobody volunteered for.
- Withhold when
- The code in question was written by someone in the room, last month. Aim this at an inheritance, not a colleague.
Selected entries
-
Must Be DNS11
It usually is.
-
Works on My Machine19
The oldest entry here, and still the shortest route to a productive argument.
-
Waiting for Godot.js20
The register's only literary reference that also compiles.
All 84 Developer Despair sprint names
The number after each is its character count. 81 of these fit Jira's 30-character cap, and 79 still fit with a short board prefix in front — see sprint names for Jira. Click one to have it stamped by the generator.
- Works on My Machine19
- Git Blame the Other Guy23
- Not My Branch13
- Works in Production19
- Probably Not My Bug19
- Wasn’t Me9
- Ask the Previous Developer26
- It Was Like That Already24
- I Inherited This16
- Who Wrote This?15
- Future Me’s Problem19
- Cannot Reproduce16
- It Worked In Staging20
- Just Don’t Touch It19
- Do Not Refactor15
- Please Don’t Look17
- It’s Probably Caching21
- Must Be DNS11
- You’re Sure It’s not DNS?25
- Must Be a Race Condition24
- Legacy by Choice16
- Technical Debt Enjoyer22
- Tech Debt Is Due16
- Held Together by Hope21
- Comments Are the Documentation30
- README was Lying16
- The Tests Know Too Much23
- Tests Are Optional18
- CI Said Maybe13
- Green Enough12
- Pipeline Roulette17
- Merge and Find Out18
- Push First, Understand Later28
- Commit and Forget17
- Revert and Pretend18
- Git Revert My Life18
- Git Reset My Expectations25
- Force Push of Despair21
- Branching Out of Control24
- Detached From Reality21
- Lost in Git History19
- Commit Archaeology18
- Blame Driven Development24
- Debugging by Astrology22
- Stack Overflow Archaeology26
- Copy Paste Engineering22
- Cargo Cult Coding17
- Trial and Error™16
- Null and Void13
- Undefined Behavior, Defined Lifestyle37
- Concurrency Is a Social Problem31
- State Management Crisis23
- One More If11
- Just One More Flag18
- Just One More Bitmap20
- Temporary Permanent Fix23
- Permanent Temporary Fix23
- Quick Fix, Long Term Consequences33
- Five Minute Refactor20
- Small Change™13
- Tiny Little Hotfix18
- Harmless Change15
- Mostly Harmless15
- Nothing Could Go Wrong22
- Past Me Was an Idiot20
- Past Me Did This16
- Past Me Had Reasons19
- Future Me Hates This20
- Somebody Approved This22
- It Passed Review16
- LGTM4
- Approved Under Duress21
- Peer Reviewed, Allegedly24
- Tested in Spirit16
- QA Has Been Notified20
- Waiting for Reproduction24
- Waiting for Godot.js20
- QA Has Feedback15
- Users Are the Test Suite24
- Customer Driven Debugging25
- Live Debugging Experience25
- Monday Morning Rollback23
- Deploy First, Panic Later25
- Git History Repeats Itself26
The other 7 genres
If this is not the register you needed, the rest are one click away. All 385 names sit together on the complete register.
Reading a list is not the same as being handed a verdict. The generator convenes a committee, deliberates briefly, and stamps exactly one name — and it remembers which ones you have already had, so it keeps serving fresh ones until the genre runs dry.
Convene the committee