Never Do Anything

The AI hype cycle in one brutal image. People are absolutely obsessed with the shiny new AI toys – Google Gemini and ChatGPT (that loading spinner icon) are getting all the attention and engagement. Meanwhile, Microsoft Copilot and Meta AI are just... sitting there at the bottom of the pool like forgotten relics. The contrast is savage: one group is having a blast in the sunshine while the other two are literally drowning in obscurity. What makes this particularly spicy is that Microsoft and Meta poured billions into their AI assistants, but they're getting absolutely zero love from users. Copilot is integrated into everything Microsoft makes, and Meta AI is shoved into Instagram and WhatsApp, yet people still prefer asking ChatGPT basic questions or testing Gemini's multimodal capabilities. That's gotta hurt the product managers responsible for adoption metrics.

Made a bold prediction on October 25th, 2025 that everyone would be "vibe coding" video games by end of 2025. Fast forward to December 14th, 2025—still waiting on that timeline upgrade. The real kicker? Dude's favorite pastime is proving people wrong, yet somehow managed to prove himself wrong in under two months. That's what I call efficient failure. The CI/CD pipeline of bad takes. When your prediction has a shorter lifespan than a JavaScript framework, you know you've achieved something special.

Remember when we thought we'd train AI to help us write code? Top panel: cute little AI cub learning from the wise software engineer master. Bottom panel: six months later, that same AI has evolved into a towering beast while we're still sitting there with our legacy code knowledge from 2019. The career progression timeline has been dramatically compressed. Took me 15 years to become a tech lead. Took AI about 15 minutes to make half my StackOverflow contributions irrelevant. But hey, at least I still know how to exit Vim. For now.

Ah yes, the pinnacle of software engineering: using a multi-billion dollar AI model to add 1 + 2. That's like hiring a NASA rocket scientist to operate your toaster. The code imports OpenAI, sets two variables, then asks ChatGPT to perform basic arithmetic that the language could do natively with a simple + operator. Congratulations, you've just made the world's most expensive calculator with the worst possible performance. Next week: using quantum computing to check if a number is odd.

Someone just discovered ChatGPT and thinks they're a full-stack developer now. They proudly announce they've built "an entire website" and when asked to share it, they casually drop a Windows file path like it's a URL. Because nothing says "I'm a web developer" quite like sending C:\Users\ben\Downloads\index.html as if everyone has access to Ben's laptop. The skull emoji really sells the confidence here. They genuinely believe they've replaced an entire development team with a chatbot that probably generated a centered div with Comic Sans. Meanwhile, actual developers are sitting there wondering if they should explain localhost, deployment, or just let natural selection run its course. The AI revolution is here, folks—and it's stored locally in someone's Downloads folder.

Oh. My. GOD! The absolute DRAMA of it all! Microsoft proudly announces that 30% of their code is now AI-generated, and then BOOM! 💥 Git operations are failing EVERYWHERE! It's like watching a corporate horror movie unfold in real-time! The grim reaper couldn't have timed his entrance better! One minute they're bragging about AI writing their code, and the next minute their Git operations are having an existential crisis. Coincidence? I think NOT! This is what happens when you replace human developers with AI that learned to code by copying StackOverflow answers without reading the comments! Reset the counter indeed—we've gone exactly ZERO days without a Microsoft AI disaster. The skeleton is all of us watching our repositories crumble while Microsoft's PR team frantically tries to explain that AI definitely wasn't responsible for this catastrophe. Sure, Jan. 🙄