How I Use Claude Code | Boris Tane
boristane.com · 2,468 words · saved by 1 readers
The research-plan-implement workflow I use to build software with Claude Code, and why I never let it write code until I've approved a written plan.
I’ve been using Claude Code as my primary development tool for approx 9 months, and the workflow I’ve settled into is radically different from what most people do with AI coding tools. Most developers type a prompt, sometimes use plan mode, fix the errors, repeat. The more terminally online are stitching together ralph loops, mcps, gas towns (remember those?), etc. The results in both cases are a mess that completely falls apart for anything non-trivial. The workflow I’m going to describe has one core principle: never let Claude write code until you’ve reviewed and approved a written plan . Th
saved by
related reading
- How I Use Claude Code | Philipp Spiessspiess.dev
- Best practices for Claude Code - Claude Code Docsanthropic.com
- How I use Claude Code on large projectslocalcan.com
- How I'm using coding agents in September, 2025 — Massively Parallel Procrastinationblog.fsck.com
- How Claude Code is built - by Gergely Orosznewsletter.pragmaticengineer.com
- A Guide to Claude Code 2.0 and getting better at using coding agents – sankalp's blogsankalp.bearblog.dev
- Don’t Outsource Your Thinkingteltam.github.io
- Using AI as a Design Engineerjakub.kr
- Claude Code for Scientists - by Patrick Mineaultneuroai.science
- Shipping at Inference-Speed | Peter Steinbergersteipete.me
- I was an AI skeptic. Then I tried plan modeyoutube.com
- How Anthropic teams use Claude Code | Claudeanthropic.com