> "Am I overthinking it?"

It feels like you answered your own questions and are also to bothered by what sloperators and assorted clout chasers think. Coding, especially "deep work", is your passion that you'll still do once you exit the rat race, vibe coding is the source of your intellectual understimulation.

To me, that solution would be simple... cut out the slop, make stuff that you'll be remembered for, that you and maybe some like-minded folks collaborate on. Who cares what some rando vibeclown thinks how long something takes? You did something you might be proud of (i. e. you didn't waste time on trivialities like so many others) and had fun along the way.

But then again my advice comes from a different corner. I don't do vibecoding. Never have, never will. I also count myself lucky that I never had to as all my professional creative endeavours happen(ed) in a freelance capacity, thereby circumventing the corporate slopmire. And I'll intend to keep it that way for control, time, and my mental health are much more important to me. I also enjoy the privilege that I don't have to live in the United States, or a country with a similar, or even worse, setup...

As for different industries... that depends on a lot factors.

Is this is for personal projects or work related? For personal, I say do what the hell you want. There's no point being deliberately miserable if you get so much enjoyment out of it. e.g. Build a compiler for BASIC that outputs LLVM bytecode! :-)

For work, you probably have to dance to someone else's tune.

I thought that this article submission a few days ago

https://news.ycombinator.com/item?id=46543516

presented a reasonable approach for using AI coding tools but still staying engaged with the code.

I am wary of hanging over the reigns entirely to AI, not just on a one-off project basis, but long-term. I don't think it's wise to rely so heavily on proprietary cloud-based applications as software development tools. Keeping one's hand on the wheel enough -- maybe like as that article describes -- should hopefully leave one still able to take over control entirely if needed.

Of course, who's to say what your employer might demand? It sounds like some people are insistent upon producing code at maximum possible speed, such that if you are still even reviewing code, much less writing some of it by hand, you are wasting time. I don't care for or agree with that notion, but it's not my place to tell someone else what to do.

as i've said (https://news.ycombinator.com/item?id=43836353) try working outside the software industry for someone who needs some software. I had a great time in the 90s working on digital audio gear.

I don't know if vibe coding is the solution to all problems. There's a lot that it can't solve, which means it's up to humans to develop the applications. Maybe you just need to find the right application to create.

It's kind of hard these days, because if you look at the world of software, corporations have enterprise systems that don't really spark any excitement for the people working on them, video games are worse than what they used to be, specifically AAA titles (indie games are cool, but they don't bring me as much excitement as AAA titles), there's like a million Android and iOS apps, most of which just aren't as... amazing as you'd want them to be.

If you really think about it, it just really comes down to the money. See, the United States is $38 trillion in debt, and as a result, I think a lot of people are struggling. If the U.S. wasn't $38 trillion in debt, I think a lot of people would have a lot more fun with software, in a way that... there would be something to create.

So, what I'm saying is, if there's a way to create software that revives society, and eases the struggle with money, that would be the thing to create.