The eternal battle: planning vs. 'just ship it'
Description
A four-panel comic strip meme depicting a conversation between two birds. In the first panel, a small, calm bird labeled 'Me' begins to say, 'I think diagrams can be good to...'. In the second panel, the bird is cut off mid-word ('...underst') by an aggressive off-screen speech bubble yelling, 'DIAGRAMS ARE SHIT'. The third panel reveals a large, loud black bird screaming 'SOFTWARE ENGINEERING IS SHIT' at the smaller bird. In the final panel, the small bird gives an annoyed, deadpan stare with a speech bubble that says, 'YOU DON'T KNOW HOW CODE'. The meme humorously captures a common conflict in development teams between those who advocate for planning and established software engineering practices (like creating diagrams) and those who dismiss them as useless. The punchline implies that the developer who aggressively rejects these practices is often overcompensating for their own lack of fundamental coding skills
Comments
10Comment deleted
The engineer screaming 'software engineering is shit' is the same one who thinks 'refactoring' means adding v2 to a function name
I dropped “let’s sketch a quick C4 diagram” in the architecture channel - five minutes later we’re debating whether ASCII art violates Twelve-Factor, someone forked PlantUML to Go, and the ops lead is shouting that “pictures aren’t idempotent.”
After 20 years in the industry, I've learned that the people who hate diagrams the most are usually the same ones who create the most incomprehensible microservice spaghetti that requires three whiteboards and a PhD in distributed systems just to trace a single API call
This perfectly captures the five stages of senior engineering grief: (1) cautious optimism about process improvements, (2) immediate self-contradiction, (3) external validation of your cynicism, (4) complete linguistic breakdown. By the time you're screaming incoherently about code, you've achieved what we call 'principal engineer consciousness' - where you've seen enough architectural diagrams become shelfware and enough 'living documentation' die on the vine that you've transcended language itself. The real joke? We all still draw the diagrams anyway, knowing full well they'll be outdated before the PR merges
Diagrams: turning monoliths into microservices spaghetti, one unreadable arrow at a time
“Diagrams are for people who can’t code” is how you end up reverse‑engineering your architecture from Jaeger traces and kubectl at 3 a.m - aka drawing the sequence diagram the hard way
Propose a C4 diagram and it devolves into ‘code is the only truth’ - from a team whose truth is a 900k‑LOC monolith and a topology only Prometheus understands
Php dev?)) Comment deleted
Explanation ? 🧐 Comment deleted
coding is shit Comment deleted