There are a lot of non developer claude code users these days. The hype about vibe coding lets everyone think they can now be an engineer. Problem is if anthropic caters to that crowd the devs that are using it to do somewhat serious engineering tasks and don't believe in the "run an army of parallel agents and pray" methodology are being alienated.
Maybe Claude Code web or desktop could be targeted to these new vibe coders instead? These folks often don't know how simple bash commands work so the terminal is the wrong UX anyway. Bash as a tool is just very powerful for any agentic experience.
If 80% of their paying customers are vibe coders then it makes sense to make IDE “easy” for them. “Hey, Claude, make a website. Don’t make mistakes.”
Or, it could serve as a textbook example how to make your real future long term customers (=fluent coders) angry… what a strategy :)
Exactly how I feel. I'm happy that more people are using these tools and learning (hopefully) about engineering but it shouldn't degrade the core experience for let's say "more advanced" users who don't see themselves as Vibe coders and want precise control over what's happening.
Run an army of parallel agents is orders of magnitude more profit per human, so they will tend to steer you towards that.
Anecdotally, all the non-technical people I know are adapting fine to the console. You don’t need to know how bash commands work to use it as you are just approving commands, not writing them.
I think Dario & crew are getting high on their own supply and really believe the "software developers out of work by end of 2026" pronouncements.
Meanwhile all evidence is that the true value of these tools is in their ability to augment & super-charge competent software engineers, not replace them.
Meanwhile the quality of Claude Code the tool itself is a bit of a damning indictment of their philosophy.
Give me a team of experienced sharp diligent engineers with these coding tools and we can make absolutely amazing things. But newbie product manager with no software engineering fundamentals issuing prompts will make a mess.
I can see it even in my own work -- when I venture into doing frontend eng using these tools the results look good but often have reliability issues. Because my background/specialization is in systems, embedded & backend work -- I'm not good at reviewing the React etc code it makes.
And even if there are lots of vibe coders who don’t like/need the information then make it a toggle for those who want/need it
[dead]
It’s funny because on one end of the spectrum you have non dev vibe coders for whom every log is noise
On the other end are the hardcore user orchestrating a bunch of agents, not sitting there watching one run, so they don’t care about these logs at all
In the middle are the engineers sitting there watching the agent go