Oriel — AI & technology worth noticing, every day.

10 Things Every Coder Has Blamed at Least Once (at Least I Have)

Web page · https://canro91.github.io/2026/10/13/Blame

Inspired by @sylwia-lask 's post on what to blame, here are 10 things every coder has blamed, or at...

First seen by Oriel on .

AI summary

A humorous list of eleven common excuses developers use to explain coding problems, from unclear requirements and legacy code to tight deadlines and AI-generated solutions.

  • The author highlights poor documentation, unclear requirements, unreadable code, existing code, and unfamiliar codebases as frequent targets of blame.
  • QA teams become scapegoats when investigating one issue exposes many existing bugs, according to the article’s anecdotal example.
  • Developers may blame unfamiliar languages, including the author’s transition from WinForms and C# to JavaScript and Knockout.js.
  • Former teammates and unavailable senior developers are easy explanations when code ownership or needed guidance is missing.
  • The bonus category blames StackOverflow, tutorials, or AI when developers cannot explain why an implementation works.

#software development #coding culture #technical debt #ai

Generated by gpt-5.6-sol. Check the original for details.

Metric trends

Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained

Reactions

Total public reactions reported by the source; distinct from points and likes.

  • DEV Community: 26, latest observation ; +7 over observed period since

Comments

Comment count reported by the source.

  • DEV Community: 10, latest observation ; +6 over observed period since

Aliases

SourceExternal IDURL
DEV Community4846665https://canro91.github.io/2026/10/13/Blame Read discussion