I’ve been meaning to write this up because it’s been surprisingly repeatable, and I wish someone had described it to me earlier.

Over the last year or so, my development speed relative to my own baseline from ~2019 is easily 20x, sometimes more. Not because I type faster, or because I cut corners, but because I changed how I use AI.

The short version: I don’t use AI inside my editor. I use two AIs in parallel, in the browser, with full context.

Here’s the setup.

I keep two tabs open:

One AI that acts as a “builder”. It gets a lot of context and does the heavy lifting.

One AI that acts as a reviewer. It only sees diffs and tries to find mistakes.

That’s it. No plugins, no special tooling. Just browser tabs and a terminal.

The important part is context. Instead of asking for snippets, I paste entire files or modules and explain the goal. I ask the AI to explain the approach first, including tradeoffs, before it writes code. That forces me to stay in control of architecture instead of accepting a blob I don’t understand.

A typical flow looks like this:

1. Paste several related files (often across languages).

2. Describe the change I want and ask for an explanation of options. Read and summarize concepts, wikipedia, etc.

3. Pick an approach. Have extensive conversations about trade-offs, concepts, adversarial security etc. Find ways to do things that the OS allows.

4. Let the AI implement it across all files.

5. Copy the diff into the second AI and ask it to look for regressions, missing arguments, or subtle breakage.

6. Fix whatever it finds.

Ship.

The second AI catches a lot of things I would otherwise miss when moving fast. Things like “you changed this call signature but didn’t update one caller” or “this default value subtly changed behavior”.

What surprised me is how much faster cross-stack work gets. Stuff that used to stall because it crossed boundaries (Swift → Obj-C → JS, or backend → frontend) becomes straightforward because the AI can reason across all of it at once.

I’m intentionally strict about “surgical edits”. I don’t let the AI rewrite files unless that’s explicitly the task. I ask for exact lines to add or change. That keeps diffs small and reviewable.

This is very different from autocomplete-style tools. Those are great for local edits, but they still keep you as the integrator across files. This approach flips that: you stay the architect and reviewer, the AI does the integration work, and a second AI sanity-checks it.

Costs me about $40/month total. The real cost is discipline: always providing context, always reviewing diffs, and never pasting code you don’t understand.

I’m sharing this because it’s been a genuine step-change for me, not a gimmick. Happy to answer questions about limits, failure modes, or where this breaks down.

Here is a wiki-type overview I put together for our developers on our team: https://community.intercoin.app/t/ai-assisted-development-playbook-how-we-ship-faster-without-breaking-things/2950

Show HN: Open-source macOS app to install and manage MCPs

Comments