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.