How strange.

Ever since AI reached a certain level of quality, I haven't been able to stop (vibe) coding. I've discovered that I really enjoy designing and building products, more than tinkering; occasionally, I come across algorithms or other technical details that I find interesting, and I switch to manual mode.

At some point in my career, I just got tired of having to read tons of documentation for fragmented libraries and frameworks, and AI is a "solution" to that.

Cynically, this could be seen as plumbing, but there's an art to designing efficient and usable products, that I personally enjoy very much.

> How strange.

People enjoy different things. Its not strange. Treating it as strange is kinda insulting, so I'd recommend that you rethink how you phrase this.

> At some point in my career, I just got tired of having to read tons of documentation for fragmented libraries and frameworks

Well that’s your problem right there, also a wider problem in programming culture. You might have had a lot more fun if you minimized dependencies and just built everything else you needed on your own. That’s fun, more fun than Vibecodin anyway. That said most programming jobs even in yesteryear was framework management so I’m not surprised people are happy to give that off to AI.

> "I just got tired of having to read tons of documentation for fragmented libraries and frameworks, and AI is a "solution" to that."

That seems like an solution to the kind of programming that is piping together little pieces of business logic with all kinds of different APIs and services all over. I agree that AI is helpful to distill the piles of documentation and things to learn.

But I mostly enjoy a different kind of programming where you work on a big complicated problem / business logic that sits mostly within the bounds of a defined language setting. The craft of finding more and more elegant, far-reaching, and correct abstractions, and then being able to build things out confidently from those well found abstractions is, in my mind, the greatest joy, and also what AI seems the worst at.

I've always enjoyed hacking on random projects and AI does that really well. Every crazy idea I've ever had can be iterated on, and takes way less time now. Sure it's awesome that I don't have to spend hours throwing together a bunch of python and bash scripts, but it just happens instantly now. That's why I actually like Copilot autocompletion for side projects, because I can build something and still save a massive amount of time tinkering with limited blockers. I wish there was a better middle ground between "one shot this" and writing everything yourself.

> I just got tired of having to read tons of documentation for fragmented libraries and frameworks

> AI is a "solution" to that

Reading AI documentation/notes is better then? Or is the implication that you can oneshot all apps/code without reading the claudespeak that explains it?

i'm the same way, and my personal projects are being created in a similar way.

i'll have a specific technical architecture in mind -- API specs, a list of cloud services, a general idea about how code should be broken into modules. i'll write it all out and let the pieces get filled in by AI.

it's not really 'vibe coding' as the term was originally envisioned where you just describe a top-level goal (e.g., "make me a new version of minecraft. no mistakes please."). it's a different level of abstraction where the models are primarily doing implementation and not design.

for me this lets me do the fun parts of designing software BUT i don't have to slog through documentation and learn a bunch of DSLs to get it going.