Me too, and I'm glad to see that this point keeps being brought up. I noticed that what shapes my satisfaction (or dissatisfaction) about working with AI depends on whether have understanding of what's being built or not.
For a prototype, it's pretty amazing to generate a working app with one or two prompts. But when I get serious about it, it becomes such a chore. The little papercuts start adding up, I lose speed as I deal with them, and the inner workings of the app becomes a foreign entity to me.
It's counterintuitive, but what's helping me enjoy coding is actually going slower with AI. I found out that my productivity gains are not on building faster, but learning faster and in a very targeted way.
Yesterday I stumbled upon the same concept for Claude Desktop and Linux [0]. I wonder why the companies themselves don't want to ship their Electron apps for Linux, Mac, and Windows. Spotify has a sensible approach: they ship the builds, although unsupported for Linux. Not ideal, but that's something. [1]
For a prototype, it's pretty amazing to generate a working app with one or two prompts. But when I get serious about it, it becomes such a chore. The little papercuts start adding up, I lose speed as I deal with them, and the inner workings of the app becomes a foreign entity to me.
It's counterintuitive, but what's helping me enjoy coding is actually going slower with AI. I found out that my productivity gains are not on building faster, but learning faster and in a very targeted way.
reply