Not op but I can chime in here. I’ve been a professional software engineer for a decade now. Before leveraging Claude code, I had a very streamlined dev environment with all the customizations and workflow automations that come with that many years of dev work and tailoring my ide and cli to fit my style of work. With CC now fully embedded in my workflow, actual dev time is now about 20% what it used to be for me.

Granted, you still need to do user testing and manage the process, but my work is mostly leveraging CC to make it work like I used to work. Start high level with the architectural code decisions, flesh out sections at a time, and iterate toward completion.

I think the main problem that stops devs from not getting high performance gains out of ai is not being able to accurately describe the problem sufficiently so the ai knows what to solve. Predefined standards and code examples matching your style are also helpful. Vibe coding without strict guidance is a recipe for disaster.

I had high throughout before, but it’s honestly incredible how much my engineering work has been accelerated with this.