Sprint
Designation Office
Genre file
BOFH Excuses
36 entries
01 / The genre 36 entries · 32 under 30

BOFH Excuses Sprint Names

Named for the Bastard Operator From Hell — Simon Travaglia's long-running sysadmin stories — and specifically for its excuse generator, a device for producing explanations that cannot be argued with because they are not quite about computers.

The construction rule is consistent enough to extend: take a real component of a real stack and give it a biological or emotional failure mode. Woodworms in Hashtable. Garbage Collector Unionized. TLS Certificate Lost Confidence. Each one names something that genuinely exists and then declines to be technical about it.

02 / Advisory Non-binding
Issue when
The sprint whose actual root cause is still unknown. This is the register's most reliable genre.
Withhold when
An audience that will fact-check it. Half the humour is the refusal to be checkable.

Selected entries

  1. Woodworms in Hashtable22

    The founding example of the construction rule. Nothing in a hashtable can rot, which is the entire joke.

  2. Microservice Became Macroservice32

    Two characters too long for Jira, and the one entry here that is really an architecture review.

  3. Daemons7

    Seven characters, no verb, no explanation offered. The genre at its shortest and its purest.

03 / The full list 26 under 26 · longest 32

All 36 BOFH Excuses sprint names

The number after each is its character count. 32 of these fit Jira's 30-character cap, and 26 still fit with a short board prefix in front — see sprint names for Jira. Click one to have it stamped by the generator.

  1. Root Dried Out14
  2. Woodworms in Hashtable22
  3. Cookies Went Stale18
  4. Kernel Got Damp15
  5. Packets Got Lost16
  6. Hash Collision Outbreak23
  7. Bitrot in Staging17
  8. Trust Store Has Trust Issues28
  9. Garbage Collector Unionized27
  10. Race Condition Won18
  11. Deadlock Became Permanent25
  12. Heap Developed Mold19
  13. Pointer Wandered Off20
  14. Null Pointer Escaped20
  15. Bytecode Got Wet16
  16. Merge Conflict Metastasized27
  17. Commit Lost Structural Integrity32
  18. HEAD Detached Itself20
  19. Repository Developed Termites29
  20. Build Server Is Haunted23
  21. Stubborn Processes18
  22. Pipeline Lost Pressure22
  23. Pipeline Started Leaking24
  24. Ether Leak10
  25. Microservice Became Macroservice32
  26. Endpoint Migrated Spontaneously31
  27. Load Balancer Developed Bias28
  28. Reverse Proxy Reversed Too Far30
  29. TLS Certificate Lost Confidence31
  30. Session Wandered Off20
  31. Regex Became Self-Aware23
  32. YAML Indentation Drift22
  33. Backbone Collapsed18
  34. Solar Flares12
  35. Cosmic Build Failure20
  36. Daemons7
04 / Other genres 7 more on file

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.

05 / Disposal End of file

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