I like this article, I think it taps into something real.

I find myself scratching real itches that would otherwise have gone left un-scratched, because the hurdle to just getting started on something was too damn high.

For example I had need for an image contact-sheet. I'm sure there exist a lot of contact sheet generators out there, but I was able to just as quickly get claude to write me a set of scripts that took a bunch of raw images, resized them down to thumbnails, extracted their meta-data, and wrote a PDF (via Typst) with filenames and meta-data, in date order.

I got lost perfecting it, hand-picking fonts etc, but it still only took an hour or so from start to finish.

It's perfect for my need, I can customise it any time I want by simply asking claude to modify it.

Did I need to be a developer to do that? Arguably yes, to know the capabilities of the system, to know to ask it to leverage image-magick and typst, to understand what the failure-modes looked like, etc.

But I dind't need to be programmer, and over time people like the OP will learn the development side of software development without learning the programming side.

And that's okay.