DEV Community

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

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

Cesar Aguirre on November 16, 2026

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...
Collapse
 
ingosteinke profile image
Ingo Steinke, web developer •

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.

Collapse
 
canro91 profile image
Cesar Aguirre •

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

Collapse
 
maame-codes profile image
Maame Afua A. P. Fordjour •

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 😂

Collapse
 
canro91 profile image
Cesar Aguirre •

You join a team, open the repo, and the only README says “TODO: add docs”

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.

Collapse
 
johnnylemonny profile image
𝗝𝗼𝗵𝗻 •

Caching and "must be a framework bug" are definitely at the top of my list, right up until git blame quietly reveals I wrote the broken line myself six months ago. 😅

My personal favorite progression during a late-afternoon debugging session is always:

  1. "Staging is acting up again."
  2. "It's definitely a stale CDN cache."
  3. "Wait... I missed an await on line 42."

Super relatable list! Which one usually takes you the longest to admit was actually your own code?

Collapse
 
canro91 profile image
Cesar Aguirre •

It's always a caching issue :D

Collapse
 
baltasarq profile image
Baltasar García Perez-Schofield • • Edited

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!

Collapse
 
canro91 profile image
Cesar Aguirre •

Ufff... #1 is a classic.

We all complain, but who likes to write docs in the first place?

Oh, errr... #4 ... Uh. Yeah. That hurts.

"That's from the original implementation" one of my favorite lines these days I'm migrating a legacy VB app :P

Collapse
 
build996 profile image
build996 •

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.

Collapse
 
nour_dude_314 profile image
nourdude • • Edited

#1. Lack of documentation: We all complained about poor or non-existent documentation, but who wants to write it in the first place?

i do want to write docs i don't get why people keep complaining abt bad docs

Collapse
 
codingwithjiro profile image
Elmar Chavez •

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).

Collapse
 
canro91 profile image
Cesar Aguirre •

People are easy to blame things that are hard to put accountability to (e.g. people who left, AI, or heck the world)

Great observation!

Collapse
 
tdude profile image
Tdude •

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...

Collapse
 
canro91 profile image
Cesar Aguirre •

LOL! Classic one too.