Make AI attack its own draft 5×: the self-critique loop's blind spot
I don't read the first draft an AI writes. First I make the AI tear its own draft apart — up to five times — and I read what's left.
Concrete code, honest costs, real failures. We try things out for ourselves, then publish what we learned — prompts, scripts, and receipts included.
How Claude, Gemini, GPT and friends behave when we actually wire them into something — not just on a benchmark.
What a thing actually costs to run. Tokens, hosting, API minutes — broken out so you can decide for yourself.
When a bet doesn't work, we say so and show the math. The corrections matter more than the wins.
I don't read the first draft an AI writes. First I make the AI tear its own draft apart — up to five times — and I read what's left.
I started this channel as a bet: if AI handles almost the entire pipeline — script, voice, visuals, edit — then doing all of it in a second language should be almost free. So I went bilingual, Japanese and English. A few videos in, I'm killing that. Here's the miscalculation, because it's one any solo builder can make.
I handed the exact same one-line prompt to Claude, Gemini, and GPT — build a landing page for a fictional app called "PlantPing" — and compared them on design, code, and generation speed.