Just like if you pressed a button to wipe out our main language stack at our job, yeah none of us would know how to do anything with assembly or machine code.
All the devs would spend a couple weeks learning assembly and go on coding. And all the non-dev vibe coders would be unable to continue.
So I don't think it's quite the same.
A couple weeks?! Really slacking, why not a few hours?
Add the violin and calculus while they're at it.
You'd probably use the first months/years to rewrite c and such anyways.
Likewise, *many* vibecoders would absolutely fail to adapt, and some would adapt, with this being their first experience. Just think of how many people started coding by using old gamemaker tools or scratch, or playing silly games. It is not the same as an LLM, but the idea that it is a gateway is definitely there. I wouldn't call LLMs "programming", because they're doing more: they're building products, which involves a lot more than programming -- hence why the skills to really thrive with LLMs are not just those of a good developer or engineer.
But weeks? I'd say less than 10% of the devs I've known my entire life would develop properly in assembly (and I'm being quite generous). Memory management, pointers, registers...just to name a few.
I think far too many people fail to realize that, with LLMs, the brain of a good problem solver, especially one with engineering background, gets much better results than someone with different characteristics. Similarly, the mind of a good product developer (and even someone with good UX inclination) does a much better job and building usable products.
This idea that LLMs are doing all of the work is frankly mind-boggling to me. It must stem from vastly different experiences of what LLMs do or whomever is using them around who says these claims. Obviously they do a lot of work, especially in the development prototyping, architecture and even ideation parts. But they only do (almost) "all of the work" in very simple or bad apps.
I've seen loads of terrible vibe-coding jobs: UX is terrible, bugs everywhere, clearly no consideration at any point for architecture (and thus the product is barely holding on). And I've seen the opposite: products that feel and act like premium stuff, because they were built by people with true love for what they do, sometimes even with a very good problem solving mind to add to that (leading to a not-so-terrible-albeit-still-barely-holding-on-but-thats-clearly-good-enough-for-the-product architecture). For every good app there are maybe 100 lovable apps that all look the same and break the second you do the wrong sequence of clicks, but the good ones do exist.
It's a tool that enables mediocrity to exist where it didn't previously, but it also empowers so many people in incredible ways. Still, you definitely need to be good at using the tool, and it definitely doesn't just happen overnight.
I imagine that was x86, which was relatively easy but also horrible. Very few people are writing assembly today because you'd need to be able to do x86-64 SIMD, ARM64, and maybe RISC-V, which are all quite a bit more complicated.
Now retired (come join the dark side, we have cookies) but still a few years away from what people would call "retirement age"
It's vaguely similar to how JS and Node enable so many people to flood the market without really knowing the underlying technology. Many of those would definitely not pick up assembly (which is the entire point I was trying to make)
0 mathematics, 0 algorithms, 0 formal languages.
Universities are pumping out "professionals" like crazy, plus nowadays they are replacing courses with new courses about AI (which might be machine learning in the best case or just prompting in the worst case).
The result is that you need to go and ask what courses where in a degree, and even then it's not really a guarantee of anything (I've met master student with bachelor in computer science who were completely unable to find the smallest number in an array).
And yet: I have not written assembly since school except for one Advent of Code challenge, and I expect it would take me quite a while to pick up a productive level of facility with it.
You're assuming people already know how to code. That's not built-in with vibecoding.
Sure, there are similarities, but while we're figuring out a FOSS solution that will run on your machine and we'll have access to more than the weights, the abstraction ladder isn't as equivalent as we think they are.
Neither is likely to go away. I do not expect it will ever be difficult to access an LLM in the forseeable future, barring massive legislation + enforcement to entirely ban them (I can run several capable coding models locally)
Nor is it likely that for developers at most companies will not have access to at least some LLM of comparably intelligence to those we have today (more advanced models may be restricted or too expensive) - right now large parts of the world economy are retooling to expand ai inference volume, not decrease it
This seems like "what if you don't have a calculator!" - and like with a calculator, there are benefits to learning things without the tool aid of course, n(including developing a sense for when things are wrong) but professionals are using the right tools for the job
Do you think its likely ?
If you scope LLM's to "frontier models", I do expect it to be an ever-growing moat. Maybe not if you work at BigCo who will pump out $X0 million/yr to gain access to it, but definitely for the singular use cases of people navigating to Claude.ai and asking a quick question. That's assuming the companies stay afloat long term to begin with.
If you open it up to open-weight models, then I question how many this will filter out. Will it be a tool valuable enough for people to overcome the large starting hump like Photoshop? Or will some future company come in and streamline the UI/UX to make them as intuitive as possible? Those are the truly interesting questions in my mind.