Designers vs Programmers: The AI Generation Wars

The devolution is complete. We went from Googling "how to reverse a string" to literally asking ChatGPT to create basic loops like we've forgotten the fundamental building blocks of programming. The crying wojak perfectly captures that moment when you realize you've outsourced your brain so hard that even a for-loop feels like rocket science without AI assistance. It's like having a calculator for so long that you forgot how to add 2+2. Except now it's "ChatGPT please help me breathe" energy. The best part? The AI probably writes better loops than we do at this point, which makes the whole situation even more tragic. We've essentially become prompt engineers who occasionally remember we used to write actual code.

The AI benchmarking cult strikes again! Everyone's obsessed with those radar charts comparing Large Language Models using some bizarre "ball turning test" metric that nobody actually understands. It's just a bunch of geometric shapes that supposedly prove one model is better than another. The joke here is that these comparison charts have become so ubiquitous in AI discussions that even though they're practically meaningless to most developers, everyone nods along pretending to understand what they're looking at. Classic tech impostor syndrome - nobody wants to be the one to ask "what the heck does this actually measure?"

PC gamers getting absolutely demolished from every possible angle. Bitcoin miners drove GPU prices to the moon, AI training suddenly needs every RTX card ever manufactured, and Micron casually dipped out of the consumer market. Meanwhile NVIDIA's just standing there watching the chaos unfold, probably calculating profit margins. And then there's "Poor Optimization" - the real villain nobody wants to talk about. Your dream PC getting absolutely kicked in the teeth because some AAA studio decided 8GB VRAM should be the minimum for their unoptimized mess. You can't even upgrade your way out of bad code. The GPU shortage era was wild. People were camping Newegg like it was a Supreme drop, paying scalper prices that would make a loan shark blush, all while game devs kept pushing "recommended specs" higher. Fun times.

Finally, a sorting algorithm with the computational complexity of O($$). Just send your array to GPT, pay a few cents, and get it back sorted. Perfect for when you need your data arranged but can't be bothered to remember how quicksort works. The best part? If your array isn't sorted correctly, you can just claim it's because the AI "didn't understand the vibe" of your integers.

Remember when we argued about text editors like they were sports teams? Now we're just watching AI companies slap version numbers on VS Code forks like they're NFTs. "My VS Code fork has more digits than yours" is the new "my dad can beat up your dad." Meanwhile, Emacs users are still configuring their first keystroke from 1976.

Ah, the evolution of our noble profession! Remember when developers were depicted as muscular gods who could write flawless code without Stack Overflow, build entire games in Assembly, send rockets to the moon, and fix memory leaks by manually adjusting pointers? Fast forward to today's reality: frantically Googling basic CSS centering (still an unsolved mystery of computer science), begging ChatGPT to fix our syntax errors, getting trapped in Vim like it's some kind of developer hazing ritual, and the classic "fix one bug, spawn three more" hydra effect. The greatest irony? Those "superhuman" developers from the past would probably spend three hours debugging their Assembly code only to realize they forgot a semicolon. We've just outsourced our impostor syndrome to AI assistants.