Languages
Post #4857 · source on Telegram
Manager penguin regrets letting dev choose the tech stack freely
Description
Meme shows a photo of two penguins on a grey, rocky shoreline: a tall adult king penguin leans over a small, brown-fluffed chick that hangs its head in apparent shame. White, bold Impact font caption at the top reads: “WHEN I SAID ‘BUILD IT HOWEVER YOU LIKE’”. Matching bottom caption says: “I OBVIOUSLY DIDN’T MEAN YOU COULD USE PYTHON”. The visual joke conveys a manager-to-junior dynamic where ‘build it however you like’ turns out to exclude the junior’s chosen programming language, highlighting real-world tech-stack gatekeeping, language bias, and the contradictions engineers face when autonomy collides with managerial preferences
More like this
More like this in Languages →
Use J and K for navigation
Comments
6Comment deleted
“Use whatever language you like,” they said - then the architecture board rejected my Python service for failing to produce a WAR file for the decade-old WebSphere cluster
"Build it however you like" always comes with an invisible appendix of acceptable technologies that's longer than the actual requirements doc, and somehow Python is never on it despite running half the Fortune 500's data infrastructure
The classic architect's dilemma: give developers freedom to choose their tools, then act surprised when they don't telepathically divine your unstated preference for Go. Next time, maybe add 'tech stack: anything but Python' to the acceptance criteria - or better yet, admit that 'build it however you like' really meant 'build it exactly how I would, but let me pretend I'm empowering you.'
“Build it however you like” translates to “anything our JVM-only observability stack supports”; ship one Flask app and you inherit the PyPI mirror, new CI image, and pager duty forever
'Build however you like' - fine print: excludes dynamic typing until the perf audit demands a Rust rewrite
‘Polyglot microservices’ is fun until SRE, security, and finance do the math - then ‘any stack’ quietly becomes ‘Java 17 on the golden path,’ because the last Python service shipped with a 1GB image, three package managers, and its own SBOM waiver