So... Mindless coding is it? The best part of coding is doing research and learning. Coding, for the pure sake of finishing the project as soon as possible with the least involvement, sounds like doing unpleasant chores.

Far from mindless, just at a different abstraction level. What should the software do, what capabilities and features, how to slice it into small increments (product management work)? What user journeys, what should the screens look like (UX work)? What architecture and components, which libraries, what communication protocols, what layering, what kind of tests, what kind of data structure and data persistence (Architect/tech lead work)? For example, for the DSL syntax i'll have claude code suggest different options, and detail out one of the proposal i like best.

Nice, but what does it mean? Are you gonna replace a group of specialists in their fields with prompts to LLM?

I have a background in coding (including assembly), worked on UX projects, as a technical architect, a product owner, and now a product manager in the last 30 years, so yes.

Some people love the act, which is fine. A good many other people just want the result.

Something something quarter-inch hole.

I agree. Vibe coding eventually just becomes repetitively QA testing the work of a bad engineer.

You can have AI write automated tests before writing the code, so it can QA itself.

You can try. What happens is it cheats you at every turn and finally admits it wasn’t testing anything when you ask why it’s still broken.

Yes, this actually happens.

So much this. I've written countless shell scripts / clis that does small things that I would not have done before.