Twitxy Saved

ryou

Verified account This account is verified. Learn more

@ryouxbt

content creator | ai researcher
rxxck Joined July 2026
50 Following 1.1K Followers 90 Posts

Latest posts 5

Pinned post

ryou Verified account @ryouxbt
This is f*cking insane. Anthropic pays the engineer who built Claude Code $1M+ a year, and he hasn't typed a single line of code since the day he uninstalled his IDE

In this 95-minute interview, he walks through the exact setup that ships 30+ pull requests a day

Prompts → Plan Mode → Parallel Agents → Self-Review Loop → Code You Never Type

step 1 → Run 5 Claudes at once - 5 tabs, each on its own copy of the repo, so the agents never step on each other

step 2 → Start agents from your phone - he kicks off a few the moment he wakes up, and they're already coding in the cloud before he opens a laptop

step 3 → Plan mode first, every time - go back and forth until the plan is right, then it one-shots the build almost every time

step 4 → Let it test itself - it runs the tests, writes new ones and launches a copy of itself to check it still works

step 5 → Claude reviews every PR - it catches about 80% of bugs before a human looks, and every mistake that repeats gets turned into a lint rule

Claude Code now writes 90% of the code at Anthropic, and 100% of his

One month, 10 to 20 PRs a day, not one line edited by hand. The agent shipped 2 bugs. By hand it would have been 20

Most engineers still type every line themselves

You don't have to

Bookmark it and watch it tonight

Then read how to wrap a loop like this into a full harness in the harness engineering guide below ↓
95:43
rari🈀 Verified account @0xwhrrari 4d
Your agent passed every test

The issue is still open

A better prompt won't fix it, because the model isn't the broken part

I broke down the harness, loop and graph around it: what each one owns, how they nest, and which one to fix first ↓ x.com/i/article/2118…
View quoted post on X
0 replies 0 reposts 20 likes 419 views View on X
ryou Verified account @ryouxbt
This is f*cking insane. Anthropic pays this engineer up to $1.2M a year because she taught AI agents to dream

In this 28-minute talk, she shows exactly how to build agents that wake up smarter than you left them

Prompts → CLAUDE.md → Memory → Dreaming → Agents That Train Themselves While You Sleep

step 1 → One CLAUDE.md file - 10 lines about your codebase and your taste, and the agent stops asking you the same questions every session

step 2 → Hand it the keys to its own memory - it decides what to remember, what to rewrite and what to forget, you never write a rule again

step 3 → Turn every process into a skill - it reads 2 lines of each and pulls the full playbook only when it needs it, so the context never bloats

step 4 → Version every memory - one bad write gets rolled back in seconds, and a hash check lets 1,000+ agents share one brain without wrecking it

step 5 → Let it dream - while you sleep, a second agent reads every transcript your fleet produced, finds the mistakes they keep repeating and rewrites their memory before morning

By the second run your agents do the job better, faster and on a fraction of the tokens

Anthropic calls this "dreaming"

Most people will spend months building this by hand

You don't have to

Bookmark it and watch it tonight

Then read how to wrap memory like this into a full harness in the harness engineering guide below ↓
30:29
rari🈀 Verified account @0xwhrrari 4d
Your agent passed every test

The issue is still open

A better prompt won't fix it, because the model isn't the broken part

I broke down the harness, loop and graph around it: what each one owns, how they nest, and which one to fix first ↓ x.com/i/article/2118…
View quoted post on X
9 replies 11 reposts 116 likes 6.7K views View on X
ryou Verified account @ryouxbt
This is f*cking insane. Anthropic poached this engineer from Google after 14 years, and now he's revealing how they merge 30,000 code changes a day without a human reading every line

In this 18-minute talk, he walks through the exact review system behind it

Code Review → Agent Review → Self-Checks → Software Factory → Lights Out

step 1 → Claude goes first - every pull request gets an agent review before a human ever opens it

step 2 → Use it like a real user - the agent runs the feature end to end in a browser and lints everything

step 3 → Hooks on every edit - they read the diff and keep fixing the PR in a loop until the checks pass

step 4 → Write your taste down - the team's best practices live in claude.md, so the agent reviews against them

step 5 → Humans check the proof, not the code - the tests it ran and what broke along the way, then they hit merge

Give an agent a way to check its own work and the quality goes up 2 to 3x

Only 5% of companies run a software factory like this today, it's heading to 34%

Most teams still review every line by hand

You don't have to

Bookmark it and watch it tonight

Then read how to build the harness that checks your agents' work in the harness engineering guide below ↓
18:42
rari🈀 Verified account @0xwhrrari 4d
Your agent passed every test

The issue is still open

A better prompt won't fix it, because the model isn't the broken part

I broke down the harness, loop and graph around it: what each one owns, how they nest, and which one to fix first ↓ x.com/i/article/2118…
View quoted post on X
8 replies 2 reposts 66 likes 2.5K views View on X
ryou Verified account @ryouxbt
This is f*cking insane. Google hired this engineer at $500K-$1.2M a year because he knows how to make AI agents write code that doesn't break

In this 41-minute workshop, he shows exactly how to build that system from scratch

Prompts → Agent Skills → Harness → Agents That Ship Without You

step 1 → Refine the idea - drop in a vague thought, the agent interviews you and comes back with 3 directions

step 2 → Write the spec - success criteria, stack and open questions locked before a single line of code

step 3 → Plan in small tasks - each one gets acceptance criteria and a list of files it's allowed to touch

step 4 → Build test-first - red to green, slice by slice, so nothing that already works breaks

step 5 → Verify and review - the agent opens the app in a browser, checks security and simplifies its own code

He open-sourced all 24 skills, and the repo is close to 100K stars

Google calls this "agentic engineering"

Most people spend weeks building this by hand

You don't have to

Bookmark it and watch it tonight

Then read how to wrap skills like these into a full harness in the harness engineering guide below ↓
41:24
rari🈀 Verified account @0xwhrrari 4d
Your agent passed every test

The issue is still open

A better prompt won't fix it, because the model isn't the broken part

I broke down the harness, loop and graph around it: what each one owns, how they nest, and which one to fix first ↓ x.com/i/article/2118…
View quoted post on X
21 replies 153 reposts 1.2K likes 89K views View on X
ryou Verified account @ryouxbt
This is f*cking insane. Google Brain founder, Andrew Ng:

"Coding agents took off faster than I would have guessed. When writing software gets 10 or 100 times faster, the code stops being the bottleneck

I now build with tiny teams of 1 to 10 people, where two people with agents cover five jobs"

In this 31-minute talk, he explains why the next decade belongs to small teams running agents, and why most companies are still using AI wrong

Code → Coding Agents → Tiny Teams → Agent-Ready Companies → Two People Doing The Work Of Fifty

Using AI doesn't mean saving an hour on one task

It means rebuilding the whole workflow around agents, the way banks turned a week of waiting into a 10-minute loan approval

Most companies will keep shaving 2% off their costs, the few who rebuild around agents will grow 50%

Worth more than any $35K AI bootcamp

Bookmark it and watch it tonight

Then read the enhanced edition of harness, loop and graph engineering in the article below ↓
32:17
rari🈀 Verified account @0xwhrrari 4d
Your agent passed every test

The issue is still open

A better prompt won't fix it, because the model isn't the broken part

I broke down the harness, loop and graph around it: what each one owns, how they nest, and which one to fix first ↓ x.com/i/article/2118…
View quoted post on X