Inspired by @sylwia-lask 's post on what to blame, here are 10 things every coder has blamed, or at least I haveβPair them with these 20+ signs you're a real coder:
#1. Lack of documentation: We all complained about poor or non-existent documentation, but who wants to write it in the first place?
#2. Unclear requirements: "That's what the use case/Jira ticket/user story said" or "It wasn't clear from the use case..." That excuse never fails.
#3. Unreadable code: "This code is a mess." Then, why do we write messy code in the first place? Or let it become messy?
#4. Existing code: "That code was already there, I just tweaked it." Or if you're working with legacy code, written in an obscure language: "That's from the original implementation."
#5. Unfamiliar codebase: "This is the first time I see this code..." Especially when you're asked to act as a rubber duck to help a coworker with a tricky bug.
#6. QA team: "QA is reporting a lot of existing issues. I just came here to fix this little corner. Now I have a full page of bug reports." True story. It happened to a friend of a friend of mine.
#7. A new (or old) language: Probably this was only me when switching from desktop apps with WinForms and C# to SPAs with JavaScript back in the early 2010s. Knockout.js, anyone else?
#8. Someone who already left the company: "I don't know. That's something $teammate did. He was the only one who touched that code." Easy to blame someone who can't defend themself. Don't be the only one touching something, by the way.
#9. A tight deadline: "That's what the best I could think of...I only had 1 day. So..." Insert shrug emoji.
#10. A more senior coder who was busy enough to help and answer my questions: "Oh, I asked $seniorCoder, but he was busy, and I didn't know what else to do, so I did what I could." Insert shrug emoji again.
And as a bonus,
#11. StackOverflow, online tutorials, and these days, AI: "I don't know... that's what I found online" or simply "AI did that."
And please don't blame Street-Smart Coding or any of my books. Jokes aside, if you want to build skills that last a career, check it out. It's the roadmap I wish I had on my journey from junior to senior coder.
Top comments (16)
Thanks for your post, and even more for the cover image. The cartoon cats are so powerful in their rage, they make even heavy vintage monitor fly into the air. The cool cat in the middle is the most modest, it only points one finger. Maybe it likes the one on the right, or it just looks cooler to keep one hand in the pocket. Hopefully it's not hiding anything dangerous.
LOL! Thanks for stopping by Ingo. I've made the cartoons part of my visual brand here. Ooooh nice catch, I didn't realize he was hiding something hahahahah
Lack of documentation hits hardest when youβre new. You join a team, open the repo, and the only README says βTODO: add docsβ π It gets even worse when the person who wrote the code has already left the company and the senior dev is too busy to answer questions. So you just read the code and hope for the best.
The funny part is that once you finally figure it out, you become the person who should write the docs. Then a tight deadline comes along and the cycle starts again π
OMG! A nightmare for every new coder...When joining a new team, improving the docs (at least the installation instructions) is a good first step to learn the development process.
Caching and "must be a framework bug" are definitely at the top of my list, right up until
git blamequietly reveals I wrote the broken line myself six months ago. πMy personal favorite progression during a late-afternoon debugging session is always:
awaiton line 42."Super relatable list! Which one usually takes you the longest to admit was actually your own code?
It's always a caching issue :D
Ufff... #1 is a classic. Sometimes it's lacking, sometimes it reads like a reference instead of showing you a simple, working example. Many times, you have the example but it doesn't go deeper...
Oh, errr... #4 ... Uh. Yeah. That hurts. "I was still learning $lang when I wrote this. I should rewrite it with more convenient and modern idioms." It's a trap!
We all complain, but who likes to write docs in the first place?
"That's from the original implementation" one of my favorite lines these days I'm migrating a legacy VB app :P
The QA example makes me wonder whether two separate questions are getting collapsed: did this change introduce the bug, and should the team fix it now? Reproducing it on the previous release answers the first, but doesn't settle the second. A pre-existing issue can still block a release if the new feature exposes it to many more users. That seems more useful to discuss than whether QA was allowed to report it.
i do want to write docs i don't get why people keep complaining abt bad docs
I just noticed one thing. People are easy to blame things that are hard to put accountability to (e.g. people who left, AI, or heck the world). I think it should be the other way around. If we took more accountability, fix, and learn from it, then why are we so afraid to take the fall? I think it links more closer to our own ego and pride. But... you know what, while typing this, I realized that a 2 minute embarrassment is negligible when compared to what you could become after (which, spoiler alert, much more stronger).
Great observation!
This is incredibly relatable! π I think every developer, regardless of experience level, has used at least a few of these excuses at some point in their career. What makes this list particularly interesting is that most of these excuses actually have some truth behind them.
Poor documentation, unclear requirements, legacy code, tight deadlines, and unfamiliar codebases are genuine challenges in software development. However, the real difference between a junior developer and a senior developer isn't necessarily that seniors never encounter these problems. It's how they respond when they do.
For example, blaming unclear requirements should eventually lead to asking better questions before implementation. Complaining about unreadable code should encourage us to leave the codebase a little cleaner than we found it. Blaming a previous developer should remind us that today's code will become someone else's legacy code tomorrow.
I particularly relate to #8 and #11. It's tempting to blame someone who has already left the company or point to AI-generated code when something goes wrong. But ultimately, we are responsible for understanding, testing, and maintaining the code we commit, regardless of where the initial solution came from.
One thing I'd add is #12: "It works on my machine!" Probably one of the oldest and most universally accepted developer excuses. π
Jokes aside, I believe these experiences are an important part of becoming a better engineer. Technical skills matter, but accountability, communication, curiosity, documentation, and the willingness to learn from mistakes are what really distinguish developers who grow throughout their careers.
The goal isn't to become a developer who never makes mistakes or needs help. It's to become one who takes ownership, learns from those mistakes, and makes life a little easier for the next person who has to maintain the code.
After all, today's excuse is potentially tomorrow's technical debt!
OMG! 100% I don't why I didn't include it.
You forgot one which is precious: -"from now on in this team we are going to mob program!"
And here I am can't focus if people talk at the same time or if there is an unpaid invoice on my table...
LOL! Classic one too.