AI in the daily workflow: where Claude actually saves time
Not every task gets better with AI. An honest accounting of where I use Claude every day — and where I deliberately don't.
Over the last few months I’ve kept an honest log: which tasks did Claude actually save me time on, and where was the supposed productivity win an illusion? The answer is sober but useful — and maybe a healthy correction to the relentless “10x productivity” claims.
Where it works
Refactoring suggestions on concrete code. I hand Claude a snippet with two or three code smells and ask for alternatives. The suggestions are rarely perfect, but they’re almost always a usable starting point — and they force me to articulate why my own solution is better when I disagree.
Translations with subject-matter context. When a customer-facing text needs to be both idiomatic and technically correct, Claude reliably helps me hit the right register. The key is supplying context: who’s reading this, in what format, for what purpose.
First drafts of structured documents. Architecture reviews, RFCs, postmortems — anywhere there’s a familiar template, Claude shortens the path from blank page to revisable draft by a factor of three to five.
Where it doesn’t
Quick lookups. For an API signature, the docs are still faster. Formulating a question, waiting for an answer, checking it for hallucinations — that’s slower than three keystrokes in the IDE.
Decisions that depend on context I haven’t written down. Should this component live in the service or the frontend? Is the migration worth the effort this quarter or next? These are questions I can’t delegate, because the answer hinges on dozens of unspoken assumptions about the team, the roadmap, and the codebase.
What I’ve learned
AI is a tool for the middle layer between “trivial” and “genuinely hard.” For trivial tasks the overhead is too high. For genuinely hard ones the AI lacks the context. But right in the middle — refactoring, first drafts, exploring an unfamiliar framework — disciplined use of AI becomes a real accelerator.
If you want to introduce AI into your team’s workflows, I’d be glad to talk. There’s no silver bullet, but there are many concrete levers — and my job is to find the ones that fit your situation.