Trying to praise architecture diagrams, but the rant escalates instantly
Description
Four - panel cartoon featuring small grey birds meant to represent "Me" sitting on a branch. Panel 1: the bird says in a pink speech bubble "I think diagrams can be good to...". Panel 2: the same bird continues "...underst" but is interrupted by a huge yellow block of text behind it reading "DIAGRAMS ARE SHIT". Panel 3: a larger, darker bird swoops in from the left yelling over a yellow background "SOFTWARE ENGINEERING IS SHIT" while the small bird watches helplessly from below. Panel 4: a close-up of the small bird looks annoyed as another yellow caption shouts "YOU DON'T KNOW HOW CODE". The meme parodies discussions in tech Slack channels where nuanced points about using architectural diagrams for shared understanding quickly devolve into loud, absolutist hot-takes dismissing diagrams, software engineering as a discipline, and a developer’s competence
Comments
7Comment deleted
I posted a C4 diagram to discuss the async boundary; within three replies it was “diagrams are waterfall,” “real engineers just grep,” and somehow we were debating tabs vs. spaces - turns out the most distributed system is consensus in Slack
The four stages of seniority: Junior who believes in documentation, Senior who's seen too many outdated diagrams, Staff who questions everything we've built, and Distinguished Engineer who's transcended language itself
Tech Twitter is the only place where 'sequence diagrams help onboarding' escalates to a referendum on whether you've ever compiled anything
This perfectly captures the three stages of a developer's relationship with architecture diagrams: Stage 1 (Junior): 'UML can help us communicate!' Stage 2 (Mid-level): 'These diagrams are always outdated anyway.' Stage 3 (Senior): *Aggressively defends the codebase as the only source of truth while simultaneously complaining that nobody understands the architecture.* The real irony? The bird yelling 'YOU DON'T KNOW HOW CODE' is the same one who refused to document anything, creating the very knowledge gap they're now weaponizing. Classic case of documentation debt coming home to roost - literally
Every “diagrams are useless” engineer becomes a PlantUML power user at 3am incident triage when the SLO is “find the TLS terminator.”
'Diagrams clarify architecture' - the mantra right before 'RTFC' in every PR review
Suggest a small C4 diagram to align boundaries and you’re suddenly “anti‑code” - declared by the same crew who document our architecture as SSH aliases, utils.jar, and Slack lore