[ryanmcl]

There's a third category emerging that I think gets overlooked in these discussions = people who couldn't program at all before, who now can. Not replacing programmers, but creating new ones.

I started coding 8 months ago at 45 with zero experience. I now have a production app processing real payments. That was genuinely impossible for someone like me before AI assistance. Not because I lacked the ability to think through problems, but because the skill floor was too high to clear while also being a parent with no spare years to invest.

The spreadsheet analogy is apt. Most of those amateur spreadsheets aren't replacing finance teams; they're solving small problems that would otherwise go unsolved. That's closer to what's happening with AI-assisted development, I feel, than the "eliminate programmers" framing suggests.

[GuB-42]

The thing is that programming is not an end goal, it is a means to a end. No one is paying you to "write code", they are paying you to make a website shat serves as a storefront, to make a video game, something for accounting,...

It turns out that in many of these cases, code is an effective way of doing it, but there may be other options. For a storefront, there are website builders that let you do it very effectively if your needs match one of their templates, there are game engines that require no code, and a lot of accounting can be done in Excel.

What I wanted to say is that maybe you could have done without code, but thanks to LLMs making code a viable option even for beginners, that's what you went for. In fact, vibe coding is barely even coding in the strictest sense of writing something in a programming language, since you are using natural language and code is just an intermediate step that you can see.

The reason programmers use programming languages is not gatekeeping, unlike what many people who want to "eliminate programmers" think. It is that programming languages are very good at what they do, they are precise, unambiguous, concise and expressive. Alternatives like natural languages or graphical tools lack some of these attributes and therefore may not work as well. Like with many advanced tools, there is a learning curve, but once you reach a certain point, like when you intend to make it your job, it is worth it.

[intelVISA]

Good lord, thank you. I'm a huge fan of LLMs, they've replaced enormous amounts of toil for me but they are not 'my job'.

If you walk to the kitchen and fry up an egg are you now a master chef? What's the difference between a surgeon and a butcher ...they both cut things?

Most shops never really needed development expertise in-house as there's no shortage of many decent tools equally suitable as code for getting machines to do most business things.

In some ways this is worse because while it's functionally the same black box intermediary as the alternative-to-code tools there's an illusion of control and more sunk cost. Do you want your sales team selling or learning JavaScript churning out goofy knock-offs for a well-solved problem?

[elzbardico]

No. it was not. You could build a passable online shop after reading a django or ruby on rails book (250, 300 pages), and a couple tutorials to deploy it in some ease to use platform.

Maybe it wouldn't be visually nice, but you would understand what you've built, which is something really really important if you are processing online payments.

[simonw]

Congratulations. This is my favorite aspect of this whole thing: LLM tooling that's helping new people break into programming by lowering the friction and learning curve.

[falkensmaize]

But the friction and learning curve is what helps you understand what you’re doing. The friction is an integral part of the process.

[PeterWhittaker]

Thoroughly insightful take!