A quiet word for those who feel like they’re falling behind
Let me guess how your morning went.
You opened your phone, scrolled through some tech feed: Twitter, Hacker News, Reddit, whatever your poison is, and within thirty seconds, you saw someone claim they built an entire SaaS product over the weekend using nothing but prompts and vibes. Then you saw a thread about a new model that makes the one you just learned obsolete. Then a CEO somewhere declared that software engineers have maybe five good years left.
You put your phone down. You picked up your coffee. And somewhere between the first sip and the second, a familiar knot tightened in your chest.
Am I falling behind? Should I be doing more? Is everything I've built going to be worthless?
Yeah. I know that feeling. I want to talk about it.
The Treadmill That Never Stops
The pace right now is genuinely absurd. It’s not just fast, it’s disorienting. Last month’s breakthrough is this month’s footnote. You barely finish a tutorial on one framework before the community has already moved on to something shinier. The vocabulary alone is exhausting: RAG, LoRA, Agents, MCP, function calling, each one demanding your attention like a toddler pulling at your sleeve.
And the showcase culture makes it worse. Every feed is a highlight reel. Everyone seems to be shipping, building, launching. Nobody posts about the afternoon they spent confused, reading the same documentation page four times. Nobody talks about the tools they tried that turned out to be useless.
It creates this illusion that there's a speeding train, and everyone is on it except you.
But Here's What I've Learned From Watching a Few Trains Go By
I've been in tech long enough to remember when the shift from classical machine learning to deep learning felt like the sky was falling. People who had spent a decade perfecting feature engineering, tuning gradient-boosted trees, building meticulous pipelines — they woke up one day and the entire conversation had moved to neural networks. A decade of expertise suddenly felt quaint.
Then deep learning itself went through its own upheavals. CNNs gave way to RNNs, then LSTMs, then attention mechanisms, then Transformers swallowed everything whole. At each turn, someone's specialty became a paragraph in a history chapter.
Then came BERT, then GPT, and suddenly pre-training plus fine-tuning was the only game in town. Another reshuffling. Another wave of existential dread.
You know what I noticed, though? The people who came through all of that, the ones who are still here and still relevant, they weren't the ones who had the best grip on any single technology. They were the ones who had learned how to learn. They had developed a kind of peripheral vision for change: the ability to sense what mattered, what was temporary, and when to invest their energy.
That skill set doesn't expire.
Not Every Wave Deserves Your Weekend
Here's something nobody tells you when you're in the thick of it: the shelf life of most technical hype is shockingly short. The vast majority of tools, frameworks, and paradigms that seem world-ending today will be footnotes in two years. Some of them will be footnotes in six months.
This doesn't mean none of it matters. It means not all of it matters equally.
And if you try to sprint after every single thing, if you treat every new announcement as a personal emergency, you will burn out. That's not a motivational cliché. It's a mechanical fact. Human beings are not designed to sustain a permanent state of urgency.
The more useful discipline isn't relentless pursuit. It's discernment. Learning to sit with the noise long enough to separate the signal. Asking: is this a real shift in how problems get solved, or is this just a new coat of paint on an old idea? Is this changing the questions we ask, or just the tools we use to answer them?
That kind of judgment is slow to build. But it's the thing that compounds.
Why I Don't Think We're Getting Replaced
I've heard the "programmers are done" narrative enough times to have an opinion on it, so here's mine: I think it's mostly wrong, and wrong in an interesting way.
The argument assumes that programming is fundamentally about producing code, and if a machine can produce code faster, then programmers lose. But that was never quite right. The hard part of software was never typing. It was figuring out what to type. Understanding messy requirements. Navigating system constraints. Making tradeoffs that don't have clean answers. Debugging not just logic errors, but conceptual errors, the kind where the code works perfectly and the product is still wrong.
AI is extraordinary at generation. It's getting better at reasoning. But it still needs someone to point it at the right problem, to validate its output against reality, to integrate it into systems that have history and politics and technical debt. That "someone" looks a lot like an engineer to me.
And here's the irony that I think gets lost in the panic: programmers are already the people closest to this technology. We're the ones working with the models every day, feeling out their edges, learning their failure modes. The anxiety often comes from proximity, when you're standing right under a wave, it looks like it's going to crush you. But proximity is also advantage. We're not watching this from the shore. We're already in the water.
A Case for Going Slow
I want to end with something that might sound counterintuitive in an industry obsessed with speed.
It's okay to be slow.
It's okay to not have an opinion on the model that dropped yesterday. It's okay to skip a hype cycle. It's okay to spend your weekend doing something that has nothing to do with AI and not feel guilty about it.
The people who build lasting careers in technology aren't the ones who mass-produce side projects on every trending tool. They're the ones who develop taste, a quiet, hard-won instinct for what matters and what doesn't. That kind of taste doesn't come from chasing everything. It comes from watching patiently, choosing deliberately, and trusting that you don't have to catch every wave to have a good ride.
So if the anxiety has been getting to you, if you've been lying awake wondering whether your skills still matter, whether you're doing enough, whether the ground beneath you is about to give way, let me say this plainly:
You are not behind. You are in the middle of a very loud, very confusing moment. And loud, confusing moments always feel more permanent than they are.
The wave will keep moving. So will you. And at your own pace, in your own way, you'll find where you stand.
I wrote this as much for myself as for anyone else. If it landed, I'd love to hear what you're going through. I suspect a lot more of us feel this way than the highlight reels suggest.
Top comments (0)