"Coding is solving puzzles".

I think everyone has heard that platitude. But it's not exactly right.

So I grew up in a very poor environment, a moldy building full of jobless addicts.

And in my town there was this shop where super poor parents could take their kids to borrow free toys and stuff.

So as a kid I remember being frustrated by these second hand jigsaw puzzles, because there were always a few pieces which had been teared up or chewed on, or were even completely missing.

That is what development is.

You pull in this seemingly awesome composer package, and that one super useful method is declared private, so you need to fork the whole thing.

Your coworker has built this great microservice in python, but instead of returning 404 not found, it returns 200 with json key/value saying "error": "not found".

There's a shitload of nicely designed templates for the company website, but half of them have container divs inside the components, the other half expect to be wrapped in container divs when included.

You're solving puzzles, but your peers are all brainless jigsaw-piece-chewers. They tried to mend a problem, but half way through got distracted, hungry and angry, started drooling over the task and used a hammer to fit in the remaining stuff.