Blog

A working order for learning Claude Code, from first prompt to shipping production code, based on teaching 600+ people and running live products solo.

I ship seven products solo with Claude Code. The code is the cheap part. This is the verification workflow that decides what actually goes live.

How I run parallel Claude Code agents across seven live SaaS products solo, what actually broke, and the review discipline that keeps merges safe.

Daniel Goldman on what's actually left for developers when AI writes most of the code: fast decisions about what to build, not typing.

A Claude council is a working method where you run several Claude instances with opposing roles before a decision, instead of asking once and getting one answer.

How Claude Code SaaS development actually works in practice, from a solo founder shipping products used by 10,000+ paying members.

A new AI model drops every few weeks. Here's why I don't migrate production systems to it on day one, and what I check first.

Running 7 SaaS products solo taught me that Claude Code is table stakes. The real edge is the workflow you build around it.

What an agent loop is, how Claude Code's /loop actually behaves, and the verification rules I use to stop a looping agent from breaking production.

How one developer ships and maintains seven live SaaS products solo in 2026 using Claude Code as an orchestration layer, not just an autocomplete tool.

How to build AI-powered SaaS products for Hebrew-speaking users, from RTL layout to native copy, based on real shipped products.

A practical look at the AI-native workflow I use to take a SaaS product from idea to live, paying users on my own - specs, code, tests, QA, and deploys with Claude Code.