> Second, even if the package’s logic is correct, I can’t help but be amazed by the fact that developers are taking on dependencies for single line functions that they should be able to write with their eyes closed. In my opinion, if you cannot write a left-pad, is-positive-integer, or isArray function in 5 minutes flat (including the time you spend Googling), then you don’t actually know how to code. Hell, any of these would make a great code screening interview question to determine whether or not a candidate can code.
> Finally, stringing APIs together and calling it programming doesn’t make it programming. It’s some crazy form of dependency hacking that involves the cloud, over-engineering things, and complexity far beyond what’s actually needed.
Obviously LLMs make the situation even more dire, but I think people are overlooking that the industry was automating itself out of programming as a craft even before them. It's just the automation involved reuse of the work of other humans.
This isn't just "a bit more automation". It's "now we don't need lift operators".
Of course, prompting an LLM to one-shot an app is a quantum leap in comparison, but c'mon, the whole direction of the field is towards automation, abstraction, convenience. It's always trended letting the programmer write less code. Have to deal with less menial tasks. So LLMs are just the latest manifestation of that motivation. And, perhaps in a decade or two, something will come along to replace LLMs, and this conversation will happen again, except even with more desperation and despair.
But while your example exists, I don't believe that's how the industry works, yet. They're not just allowing laymen to one-shot their production software. Certainly some teams may be trying that, and some indie devs have made good money already selling vibecoded software. But I don't think the technology is good enough to auto-generate professional code at scale, without human oversight. Give it another eighteen months.