Levels of abstraction: programmers versus those who write their tools
Description
Two - panel cartoon meme in bright, pastel colors. Panel 1: a small, white, smiling blob-character wearing blue overalls sits at a chessboard with only two pieces; over its head is the caption text “programmer who programs programs”. Panel 2: the viewpoint zooms out to reveal a huge stone statue-like figure with a CRT monitor for a head, seated cross-legged and gently patting the smaller blob; the caption reads “the programmer who programmed the programming program”. A smiling sun and puffy clouds complete the idyllic scene. The joke contrasts everyday application developers with the deeply knowledgeable engineers who build compilers, IDEs, and other meta-programming toolchains, illustrating the hierarchy of abstractions within software engineering
Comments
16Comment deleted
Me spending a sprint refactoring microservices for “clean architecture,” while somewhere a compiler engineer commits an escape-analysis tweak that deletes half my abstractions and pats me for the CPU cycles I almost saved
The guy who wrote the compiler in assembly thinks he's enlightened until he meets the person who toggled in the bootstrap loader using front panel switches
It's turtles all the way down until you hit the one person who still maintains the C compiler - be nice to them
The real flex isn't writing elegant code - it's writing the compiler that makes everyone else's 'elegant' code possible. While most developers argue about tabs vs spaces, these legends are defining what constitutes valid syntax in the first place. They're the architects who built the chess board, wrote the rules, and then casually mentioned they also invented chess notation. It's the ultimate 'I use Arch btw' energy, except they literally wrote Arch. Or as they say in compiler circles: 'You merely adopted the abstraction layers. I was born in them, molded by them - I didn't see user-facing code until I was already a man.'
Architects tower over UML chessboards plotting CAP theorem endgames; coders cradle that one leaky service like a pawn about to promote - or crash
We call ourselves full-stack; the compiler engineer wrote the stack frames, SSA, and optimizer that make our bad ideas look fast
Your biggest bug is a null pointer; theirs is a stage-2 bootstrap miscompile that only appears when -O3 inlines the register allocator into itself
It's a joke about Kite? Comment deleted
I think it's a joke about IDEs, compilers, linters, etc Comment deleted
linters? Comment deleted
He meant linkers Comment deleted
no, he didn't > "those help with auto completion" Comment deleted
I think linter is for rules of code format. Comment deleted
Did you mean deephell's text editor? Comment deleted
That's what I was thinking when I first got to the computer. Like, how do I create a program? What is the first program where programs were created? So I literally googled and downloaded Pascal and I had no idea what is this. Comment deleted
Like a Philosophy question 😂 Comment deleted