Unless your gunning for a top position as a vibe coder, this whole concept of "falling behind" is just pure FOMO.
Unless you're in web dev because it seems like that's one of the few domains where AI actually works pretty well today.
???
The classic line (which I've quoted it a few times here) by Charles Mackay from 1841 comes to mind:
"Men, it has been well said, think in herds; it will be seen that they go mad in herds, while they only recover their senses slowly, and one by one.
"[...] In reading The History of Nations, we find that, like individuals, they have their whims and their peculiarities, their seasons of excitement and recklessness, when they care not what they do. We find that whole communities suddenly fix their minds upon one object and go mad in its pursuit; that millions of people become simultaneously impressed with one delusion, and run after it, till their attention is caught by some new folly more captivating than the first."
— Extraordinary Popular Delusions and the Madness of Crowds
And rest of my field. Automated tools do part of work. AI probably some, but not enough of actually verifying findings and then properly explaining the context and implications.
Earlier this year the ecosystem was still a mess I didn't have time to untangle. Now things are relatively streamlined and simple. Arguably stable, even.
I feel behind, sure, but I also don't think people on the bleeding edge are getting that much more utility that it's worth sinking dozens or hundreds of my very limited hours into understanding.
Besides, I'm a C programmer. I'll always be several decades behind the trend. I'm fine with that.
It's high dose copium. Please keep the good times rolling! Buy my books! Sub to my stack!
Meanwhile, with local models, local RAG, and shell scripts, I am wandering 3D immersive worlds via a GPU accelerated presentation layer I vibe coded with a single 24GB GPU. Natural language driven Unreal engines are viable outputs today given local only code gen.
Karpathy and the SV VC world thought this would be the next big thing to pump for a decade plus; like web pages and SaaS. But the world is smarter, more adept at catching up that it is just state management in a typical machine. The semantics are well known and do not need re-invention.
The hilarity at an entire industry unintentionally training their replacements.
I've tried at every new model release (that can run on my 24GB card) and everything is still entirely useless.
I'm not writing web stuff though.
what drugs are you using?
Sure, I can write code manually, but in my case I’m working full time on my own SaaS and I am absolutely faster and more effective with AI. It’s not even close. And the gains are so extreme that I can’t justify writing beautiful hand-crafted artisanal code anymore. It turns out that code that’s “good enough” will do, and that’s all I can afford right now.
But long-term, I don’t know that I want to do that work, especially for some corporation. It feels like the difference between being a master furniture craftsman, and then going work in an IKEA factory.
AI supported coding is like four wheel drive: it will get you stuck but in harder places. The people that use these tools to reach above the level of their actual understanding are creating some very expensive problems. If you're an expert level coder and you use AI to speed up the drudgework you can get good mileage out of them, but if you're a junior pretending to be a senior you're about to cost your employer a lot of $ hiring an actual senior.
And for good reason - the ill disciplined human body optimises for short term benefits. The disciplined body recognises the flaw in this and thinks much broader.
And its actually not well paid because client now has the expectation that mostly everything is now done, you have to just only fix few things and you even have AI at your disposal so expect that you just write a better magic prompt.
I think actually often its faster and cheaper to start from scratch or at least rewrite whole module (of course still with AI with just better vibe engineering rather than vibe coding).
It's similar with house renovation - often its just cheaper and faster to tear whole building down rather than fixing it.
I'm just very curious where we are at the moment with in this profession.
However it was just adding pile of feature after features without taking time to refactor it. Client most likely did some few different attempts to add some specific feature or fixing something and there was a lot of dead code that haven't been used. This dead code actually confused AI and often tried to modify part of code that have been abandoned.
There was completely no tests. No performance tests. And some part of my job was to improve performance (cv/ai model inference) and robustness (crashes, memory leaks).
I think AI is fine and useful but whats bad with such vibe coded project if somebody hand over to you is you have completely no clue what part of the code are written/designed properly with good foundation if previous developer didn't test extensively and didn't refactor continuously. Even worse if you cannot talk to previous developer responsible for the project.
Second, do you actually want to do that work? I don’t. I spent years working as a freelancer and I cleaned up a lot of shitty code from other freelancers. Not really what I want to spend my 50s doing.
What burden are you talking about? Using LLMs isn't that hard, we have done harder things before.
Sure, there will be people that refuses to "let go" and want to keep doing things the way the like them, but hey! I've been productive with vim (now neovim) for 25 years and I work with engineers that haven't mastered their IDEs at the same level. Not even close!
Sure, they have have never been "burdened" by knowing other editors before those IDEs existed, but claiming that I would have it harder to use any of those because I've mastered other tools before is ridiculous.
I'm very happy being decades behind the curve here. C's slowness is perfect for me.
I took this approach when the Kubernetes hype hit and it never limited my prospects.
As long as more software developers are needed your logic obviously holds, it is irrelevant whether you are a master. There are enough jobs for "good enough". But what if "good enough" is no longer a viable economic niche? Since that niche is now entirely occupied by LLMs.
Imagine someone in the 90s saying "if you don't master the web NOW you will be forever behind!" and yet 20 years later kids who weren't even born then are building web apps and frameworks.
Waiting for it to all shake out and "mastering" it then is still a strategy. The only thing you'll sacrifice is an AI funding lottery ticket.