Tech stack Memes

The question "what are you writing in?" used to have a straightforward answer—Java for enterprise, JavaScript for web, maybe C++ if you were doing systems work. But now? WebAssembly is running in browsers, Rust is eating everything, Go is handling backend services, and Python somehow does both AI and scripting. The joke hits because even developers themselves can't keep up with the tech stack explosion. When someone asks what you're coding in, you might genuinely need to consult your "agent" (whether that's your AI coding assistant, your manager, or literally just checking which terminal tab you're in). The response "will have to ask my agent" is both absurd and relatable—we've reached peak abstraction where developers are so removed from the metal that they're not even sure what language their code will compile to anymore. Fun fact: With tools like Copilot and ChatGPT writing chunks of code, some devs really ARE asking their "agent" what language they should use. The future is weird.

Two people meet and think they've found their soulmate because they both "love coding." Sweet, right? Wrong. Turns out one person's stack is Python, VS Code, Git, Docker, and Postman while the other is rocking ChatGPT, Unity, Figma, and... whatever that orange thing is. They're basically speaking different languages at this point. It's like saying you both love food but one person only eats sushi and the other exclusively consumes gas station hot dogs. Sure, you both technically "love coding," but you'll never agree on anything ever again. Good luck collaborating on that project.

When two devs meet and say they both love coding, it's all sunshine and rainbows until you find out one writes Python web apps while the other programs industrial PLCs in ladder logic for Siemens controllers. Suddenly that "shared passion" feels like comparing a Tesla to a forklift—both have wheels, technically. The guy's side shows industrial automation systems (LD, FBD, ST, IL—IEC 61131-3 languages for you normies) with brands like ABB, Honeywell, and Yokogawa. Meanwhile, she's rocking the modern dev stack: Python, VS Code, Git, Docker, ChatGPT. Two completely different universes that both call themselves "coding." It's like one person is keeping nuclear power plants running while the other is building a to-do app with 47 npm dependencies. Both valid. Both coding. Both would absolutely hate each other's job.

The eternal struggle of every developer at project kickoff: the dark wolf wants to install that experimental framework that's still in alpha, configure a custom build pipeline with seventeen microservices, and use the latest TypeScript features that aren't even officially released yet. Meanwhile, the white wolf just wants to npm install something that has actual documentation and won't break during a production deploy at 3 AM. Spoiler alert: the dark wolf usually wins during the initial setup, then the white wolf gets the last laugh when you're desperately searching Stack Overflow three weeks later because the bleeding edge tool you chose has exactly 47 GitHub stars and the last commit was "fix: everything is broken lol." The responsible choice is boring, but at least it ships. The exciting choice is... well, it's exciting until your CI/CD pipeline becomes a crime scene.

Look, if you're constantly hyping up your tech stack like it's the second coming of Silicon Valley, you're not being innovative—you're just advertising that you can't write decent code without seventeen layers of abstraction doing the heavy lifting. Real skill is making things work with whatever rusty toolbox you've got, not needing the latest framework-of-the-week to ship a basic CRUD app. The devs who actually know what they're doing? They're too busy fixing your mess to brag about their setup on LinkedIn.

Two developers meet cute at a bookstore. They both love coding! Perfect match, right? Wrong. Guy's rocking the Python-VS Code-Git-Docker-Rust starter pack while she's rolling with ChatGPT-Unity-some design tools-and what appears to be the entire Adobe suite. It's like watching a backend engineer try to date a creative AI-powered game dev. They both love coding the same way people "love music"—technically true, but one's listening to death metal while the other's making lo-fi beats with an AI DJ. The real question isn't which one you are. It's whether you've ever been on a date where you realize your idea of "coding" involves completely different ecosystems, and now you're stuck explaining why your 47 Docker containers are actually very organized, thank you very much.

While everyone's out here fighting over whether React is better than Vue, or if Rust will replace C++, or debating the merits of microservices versus monoliths, there's a silent army of COBOL developers quietly cashing checks that would make a FAANG engineer jealous. Born in 1959, COBOL is literally older than most programming paradigms we argue about today. Yet it still runs 95% of ATM transactions and processes about $3 trillion in commerce daily. Banks, insurance companies, and government agencies are desperate for COBOL devs because nobody learns it anymore—supply and demand at its finest. So while the tech bros are having a royal rumble about the hottest new JavaScript framework that'll be obsolete in 6 months, COBOL devs are just vibing, maintaining legacy systems, and getting paid premium rates to touch code that's been running longer than they've been alive. Job security? Try career immortality .