10 Developer Canon Events, Ranked From S Tier to C Tier

If you clicked on this, you’re probably a developer. Or you’re in the process of becoming one. Either way, welcome. You’re about to go through the same painful, slightly embarrassing, weirdly universal experiences every developer goes through. At some point, I realized we all collect the same stories. Different languages, different stacks, different jobs, same pain. It’s almost funny how predictable it is. So here’s a ranking of 10 developer canon events, from S tier all the way down to C tier , based on how common they are and how deeply they scar your brain. 1. “I’ll add tests later.” The deadline is tomorrow. The feature works. And “later” feels like a reasonable plan. It never is. Every developer has said this at least once, and most of us have said it more than once. Untested code has a way of surviving just long enough to become someone else’s problem, and then eventually your problem again. Somewhere in almost every codebase, there’s a little graveyard of comments like: TODO: ad