> 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.

*Many* devs would be completely incapable of learning assembly. Heck, many would be unable to learn C.

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.

> All the devs would spend a couple weeks learning assembly and go on coding

A couple weeks?! Really slacking, why not a few hours?

Add the violin and calculus while they're at it.