Software Then Vs Software Now

The existential crisis every developer faces when AI enters the chat. We spend decades perfecting the art of turning vague client requirements into functional code, only for some robot to ask if we can even do our jobs anymore. That moment of self-reflection hits hard because we all know the truth – half our job is deciphering what "make it pop" actually means while the other half is Googling syntax we've forgotten for the fifth time this week. Meanwhile, ChatGPT is sitting there smugly generating entire codebases from prompts like "website but pretty pls." The audacity.

Nothing quite like spending four years pulling all-nighters, drowning in student debt, collecting certifications like Pokémon cards, only to watch ChatGPT casually do your job in 3 seconds. The calm acceptance on that face? That's the look of someone who just realized their Computer Science degree is now worth about as much as a Blockbuster membership card. But hey, at least you learned data structures and algorithms, right? Surely AI can't... *checks notes* ...oh. Oh no. The real kicker? Junior devs are out here competing with AI that doesn't need health insurance, never asks for raises, and doesn't spend 2 hours a day in stand-ups discussing blockers. We've officially entered the timeline where "prompt engineer" is unironically a more stable career path than software engineer.

Spent three hours debugging only to end up asking ChatGPT, Claude, and Gemini the same question with slightly different wording hoping one of them accidentally gives you the right answer. Modern debugging isn't about knowing how to fix problems—it's about knowing which AI to sweet-talk into fixing them for you. The real skill is crafting the perfect prompt that doesn't make the AI say "That sounds challenging, have you tried reading the documentation?"

Changing "loading..." to "thinking..." is literally the entire business model of half the AI startups that raised millions in 2023-2025. No model improvements, no actual AI innovation—just a UI text swap and suddenly you're "leveraging advanced agentic reasoning systems." VCs saw that ellipsis animation paired with the word "thinking" and started writing checks faster than a poorly optimized O(n²) algorithm. The best part? It probably works because users genuinely perceive the app as smarter when it says "thinking" instead of "loading." Same API call to OpenAI's GPT, same 3-second delay, but now you're an "agentic AI platform" instead of just another wrapper. Marketing genius meets minimal viable product in its purest form.

The job market speedrun nobody asked for. You grind through four soul-crushing interviews, negotiate salary, survive onboarding, maybe even figure out where the good coffee is... and then three months later you're training your own replacement that runs on electricity and doesn't need health insurance. The real kicker? That AI probably used your own code commits to learn how to do your job. Talk about adding insult to injury. At least Harold here is taking it well—that smile in the second panel is either zen-level acceptance or he's already pivoting to become a prompt engineer. Fun fact: The average developer now has a shorter job lifespan than a JavaScript framework. Which is saying something.

The financial devastation of modern AI tooling subscriptions hits different. Dad's paying $20/month for Claude, another $20 for ChatGPT Pro, probably $10 for Cursor, and the family budget is looking like a deprecated codebase—absolutely broken. The irony? These AI tools are supposed to make us more productive and save money, but here we are eating scraps in a condemned building because every developer needs their premium AI assistant just to autocomplete a for-loop. The SaaS subscription model strikes again—death by a thousand monthly charges. Fun fact: If you're subscribed to all three, that's $50/month or $600/year just to have AI write your commit messages and explain regex patterns you could've Googled. But let's be real, none of us are canceling these subscriptions anytime soon.