10 Things Every Coder Has Blamed at Least Once (at Least I Have) 0 ▲ Just Some Code 1 hour ago · Tech · hide · 0 comments Inspired by a post I found today on dev.to and to hit my daily 10-idea list, 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… No comments yet. Log in to reply on the Fediverse. Comments will appear here.