Programmer: Mathematician or Glue-Code Monkey?

Level 1: The Castle Made of Borrowed Bricks

Someone announces, very seriously, that his job is so hard it requires the brain of a great mathematician. His friend points out what the job actually looks like: taping together pieces other people built, then patching the wobbly bits until the inspector says "fine." Instead of arguing, the man just yells "Hey! I'm a mathematician!" It's the kid who claims to be a master chef and is then spotted microwaving pizza rolls — and when teased, shouts "I'm a chef!" twice as loud. The louder the title, the funnier the microwave beep behind it; what makes everyone laugh is that holding onto the fancy version of ourselves is so very human.

Level 2: The Vocabulary of Disillusionment

• Framework — a pre-built application skeleton (Django, Spring, React) that dictates structure; you fill in the blanks. The tweet's «говнофреймворки» ("crap-frameworks") is how they're affectionately known on bad days.
• Library — a smaller reusable component you call from your code. Real projects stitch together dozens.
• Glue code — the unglamorous code connecting frameworks and libraries: data reshaping, adapters, configuration. It's most of most jobs, and almost none of any curriculum.
• QA approval — Quality Assurance testing your change and signing off. "Fix until QA approves" describes the real development loop: submit, get a bug back, patch, resubmit — convergence by iteration rather than correctness by construction.

The early-career arc this tweet compresses: you arrive expecting elegant algorithms (you did just spend months on binary trees for interviews), and your first ticket is "the date is formatted wrong on the invoice page, but only in Safari." Both feelings that follow are normal — the deflation, and the eventual realization that making twenty mismatched components behave like one coherent system is its own genuinely hard skill, just not the one on the brochure.

Level 3: The Identity Crisis in Three Lines

This tweet by Alexander Taran (@alcotaran) is a perfectly compressed morality play about the gap between programming's self-mythology and its daily practice. The structure is classic thesis–antithesis–ego-collapse:

— Программирование — это самая трудная из массовых профессий, нужно обладать способностью первоклассного математика к абстракции и логическому мышлению. (Programming is the hardest of mass professions; you need a first-class mathematician's capacity for abstraction and logical thinking.)

— Да ты же просто склеиваешь говнофреймворки с говнобиблиотеками и фиксишь, пока QA не зааппрувит. (But you just glue crap-frameworks to crap-libraries and fix it until QA approves.)

— Ты чё, пёс, я математик! (Watch it, dog — I'm a mathematician!)

The final line is the kill shot: confronted with an accurate description of his job, the programmer doesn't refute it — he can't — so he escalates to street-slang aggression while restating the prestige claim. The register collapse (from lecture-hall vocabulary about "abstraction and logical thinking" to «ты чё, пёс») mirrors the actual collapse of the argument. He defends the mathematician identity in the language of someone defending a parking spot.

The discourse being skewered is real and load-bearing. The industry's origin story runs through Turing, Dijkstra, and Knuth; CS curricula lead with automata and proofs; interview gauntlets demand whiteboard algorithmics. Then the job starts, and the work is overwhelmingly integration: wiring a web framework to an ORM to a payment SDK, reading half-true documentation, upgrading dependencies that break each other, and iterating on a ticket until QA flips it to approved. Studies of real codebases keep confirming that most application code is glue and configuration, not algorithms. The punchline's defensive rage lands because both speakers are right at once — the capacity for rigorous abstraction genuinely matters (someone has to understand why the two crap-libraries disagree about timezone handling), yet the texture of the day rarely exercises it in mathematician form. The cognitive dissonance between "what I trained for" and "what I invoice for" is a quiet engine of industry-wide imposter syndrome — and the loudest "I'm a mathematician!" often comes from whoever most recently spent four hours fixing a YAML indent. Note also the QA detail: the loop terminates not when the code is correct but when QA approves — an empirical, social definition of "done" that no proof system would accept, which is exactly the second speaker's point.