How do you review code at Amp? Ask the agent first.
“Give me irrefutable proof that this works end-to-end.” — @thorstenball
21 people, a single meeting a week, no quarterly goals, no pull requests, no mandatory code review, no titles (except one dictator), a hundred releases a day, bugs fixed in minutes, famous for killing features.
@sqs and @thorstenball on how the Amp team works:
Amp retweeted
You can now self-host orbs.
It's free for individuals and teams.
ampcode.com/news/self-hosted…
Think you get it, but you’re at a 200+ person company where most people don’t?
@thorstenball and @sqs’s advice: “Kill the gossip channel.”
21 people, a single meeting a week, no quarterly goals, no pull requests, no mandatory code review, no titles (except one dictator), a hundred releases a day, bugs fixed in minutes, famous for killing features.
@sqs and @thorstenball on how the Amp team works:
We're experiencing infrastructure issues.
Investigating.
You can see the current status here: ampcodestatus.com/
Amp is built by a team of 21, with revenue the size of competitors that have 30, 40 or 50 times the staff.
“This is what a lot of other companies in the future will look like.” — @sqs
21 people, a single meeting a week, no quarterly goals, no pull requests, no mandatory code review, no titles (except one dictator), a hundred releases a day, bugs fixed in minutes, famous for killing features.
@sqs and @thorstenball on how the Amp team works:
“But the code review process is what creates the risk.”
@thorstenball and @sqs on 4,000-line PRs on a Friday, branches nobody remembers, and what continuous integration actually means.
21 people, a single meeting a week, no quarterly goals, no pull requests, no mandatory code review, no titles (except one dictator), a hundred releases a day, bugs fixed in minutes, famous for killing features.
@sqs and @thorstenball on how the Amp team works:
On graduation day, a Navy aircraft mechanic checks the jet alone. No senior mechanic. Not even the pilot.
@sqs on why skin in the game makes people better, and what that means for code review.
21 people, a single meeting a week, no quarterly goals, no pull requests, no mandatory code review, no titles (except one dictator), a hundred releases a day, bugs fixed in minutes, famous for killing features.
@sqs and @thorstenball on how the Amp team works:
“You defined those teams based on the capabilities of humans in 2019.”
When agents let every engineer reach 10× further, the old team boundaries start to collide. @thorstenball and @sqs on bigger fish in the same pond.
21 people, a single meeting a week, no quarterly goals, no pull requests, no mandatory code review, no titles (except one dictator), a hundred releases a day, bugs fixed in minutes, famous for killing features.
@sqs and @thorstenball on how the Amp team works:
You can also watch it on YouTube: youtu.be/deiLxNZH_DM
Or listen to it on Spotify: open.spotify.com/show/1AL44J…
If you want to listen to all of them: ampcode.com/podcast
Amp retweeted
You can now share your Amp runner's desktop
ampcode.com/news/runner-desk…
Amp retweeted
You can use your Claude plan in Amp now. Free and open to everyone.
(By very very very very popular request.)
ampcode.com/news/use-your-cl…
Amp retweeted
Who wants macOS orbs?
ampcode.com/morbs
“Planning is dead. Or it's going to change 99.99%.”
The hot take @sqs would add to @thorstenball’s list.
Would you prefer to save money with dial-up when your competitors are using fiber?
Recorded on Hot Take Thursday, @sqs and @thorstenball are back with a new Raising An Agent. In this episode they discuss how cheaper models end up costing more, why they do not not wait for agents, running evals in Orbs, and the hot takes Thorsten left out of his X post last week.
00:00 Intro: Engineers who forget the history of technology
01:55 Hot Take Thursday & a €50-a-week token budget
05:14 Why cheap models cost more than frontier models
08:11 Token budgets & who gets priced out
14:06 Disrupt yourself with small teams & unlimited tokens
16:38 Agents go horizontal across the software lifecycle
20:56 Rollouts, bug reports & "I'm feeling Pucky"
23:53 Code review, monorepos & other walls around the agent
25:30 How to show a cautious company what agents can do
29:48 Why most people haven't seen what agents can do
31:57 Don't wait for your agent
33:38 Simple evals & agents testing agents in Orbs
38:27 Why Amp has runners too
40:47 Follow your energy & stay aligned
46:33 The hot take Thorsten left out
54:14 Do languages & frameworks still matter?
Imagine the collective hours lost to reading AI-generated Slack messages, PRDs, and slide decks.
@thorstenball and @sqs discuss how AI can meaningfully accelerate product development -- just not by bolting it onto old rituals and processes.
Would you prefer to save money with dial-up when your competitors are using fiber?
Recorded on Hot Take Thursday, @sqs and @thorstenball are back with a new Raising An Agent. In this episode they discuss how cheaper models end up costing more, why they do not not wait for agents, running evals in Orbs, and the hot takes Thorsten left out of his X post last week.
00:00 Intro: Engineers who forget the history of technology
01:55 Hot Take Thursday & a €50-a-week token budget
05:14 Why cheap models cost more than frontier models
08:11 Token budgets & who gets priced out
14:06 Disrupt yourself with small teams & unlimited tokens
16:38 Agents go horizontal across the software lifecycle
20:56 Rollouts, bug reports & "I'm feeling Pucky"
23:53 Code review, monorepos & other walls around the agent
25:30 How to show a cautious company what agents can do
29:48 Why most people haven't seen what agents can do
31:57 Don't wait for your agent
33:38 Simple evals & agents testing agents in Orbs
38:27 Why Amp has runners too
40:47 Follow your energy & stay aligned
46:33 The hot take Thorsten left out
54:14 Do languages & frameworks still matter?
Only care about writing the code?
@thorstenball: “that game is over.”
Would you prefer to save money with dial-up when your competitors are using fiber?
Recorded on Hot Take Thursday, @sqs and @thorstenball are back with a new Raising An Agent. In this episode they discuss how cheaper models end up costing more, why they do not not wait for agents, running evals in Orbs, and the hot takes Thorsten left out of his X post last week.
00:00 Intro: Engineers who forget the history of technology
01:55 Hot Take Thursday & a €50-a-week token budget
05:14 Why cheap models cost more than frontier models
08:11 Token budgets & who gets priced out
14:06 Disrupt yourself with small teams & unlimited tokens
16:38 Agents go horizontal across the software lifecycle
20:56 Rollouts, bug reports & "I'm feeling Pucky"
23:53 Code review, monorepos & other walls around the agent
25:30 How to show a cautious company what agents can do
29:48 Why most people haven't seen what agents can do
31:57 Don't wait for your agent
33:38 Simple evals & agents testing agents in Orbs
38:27 Why Amp has runners too
40:47 Follow your energy & stay aligned
46:33 The hot take Thorsten left out
54:14 Do languages & frameworks still matter?
Is your agent still just the thing that writes code?
@thorstenball says the latest models let you aim much higher:
“Previously the agents went fully vertical in the stack… But now I think it's time to go horizontal, meaning the whole lifecycle.”
Would you prefer to save money with dial-up when your competitors are using fiber?
Recorded on Hot Take Thursday, @sqs and @thorstenball are back with a new Raising An Agent. In this episode they discuss how cheaper models end up costing more, why they do not not wait for agents, running evals in Orbs, and the hot takes Thorsten left out of his X post last week.
00:00 Intro: Engineers who forget the history of technology
01:55 Hot Take Thursday & a €50-a-week token budget
05:14 Why cheap models cost more than frontier models
08:11 Token budgets & who gets priced out
14:06 Disrupt yourself with small teams & unlimited tokens
16:38 Agents go horizontal across the software lifecycle
20:56 Rollouts, bug reports & "I'm feeling Pucky"
23:53 Code review, monorepos & other walls around the agent
25:30 How to show a cautious company what agents can do
29:48 Why most people haven't seen what agents can do
31:57 Don't wait for your agent
33:38 Simple evals & agents testing agents in Orbs
38:27 Why Amp has runners too
40:47 Follow your energy & stay aligned
46:33 The hot take Thorsten left out
54:14 Do languages & frameworks still matter?
Don't wait for your agent. Let it wait for you.
@thorstenball on why he never watches agents work: let them take as long as they need to comprehensively test changes in orbs, and focus on something else.
They don’t take up resources, or cost anything while they wait. We get back to them once we’re ready.
Would you prefer to save money with dial-up when your competitors are using fiber?
Recorded on Hot Take Thursday, @sqs and @thorstenball are back with a new Raising An Agent. In this episode they discuss how cheaper models end up costing more, why they do not not wait for agents, running evals in Orbs, and the hot takes Thorsten left out of his X post last week.
00:00 Intro: Engineers who forget the history of technology
01:55 Hot Take Thursday & a €50-a-week token budget
05:14 Why cheap models cost more than frontier models
08:11 Token budgets & who gets priced out
14:06 Disrupt yourself with small teams & unlimited tokens
16:38 Agents go horizontal across the software lifecycle
20:56 Rollouts, bug reports & "I'm feeling Pucky"
23:53 Code review, monorepos & other walls around the agent
25:30 How to show a cautious company what agents can do
29:48 Why most people haven't seen what agents can do
31:57 Don't wait for your agent
33:38 Simple evals & agents testing agents in Orbs
38:27 Why Amp has runners too
40:47 Follow your energy & stay aligned
46:33 The hot take Thorsten left out
54:14 Do languages & frameworks still matter?
“I thought you guys were all about non-local dev, so why do you have the runners?”
@thorstenball on runners, which run Amp agents on machines you own: a Raspberry Pi at home, a lab of test hardware, GPU boxes, a macOS build machine.
“I think runners on different machines are non-local too, you know?”
Would you prefer to save money with dial-up when your competitors are using fiber?
Recorded on Hot Take Thursday, @sqs and @thorstenball are back with a new Raising An Agent. In this episode they discuss how cheaper models end up costing more, why they do not not wait for agents, running evals in Orbs, and the hot takes Thorsten left out of his X post last week.
00:00 Intro: Engineers who forget the history of technology
01:55 Hot Take Thursday & a €50-a-week token budget
05:14 Why cheap models cost more than frontier models
08:11 Token budgets & who gets priced out
14:06 Disrupt yourself with small teams & unlimited tokens
16:38 Agents go horizontal across the software lifecycle
20:56 Rollouts, bug reports & "I'm feeling Pucky"
23:53 Code review, monorepos & other walls around the agent
25:30 How to show a cautious company what agents can do
29:48 Why most people haven't seen what agents can do
31:57 Don't wait for your agent
33:38 Simple evals & agents testing agents in Orbs
38:27 Why Amp has runners too
40:47 Follow your energy & stay aligned
46:33 The hot take Thorsten left out
54:14 Do languages & frameworks still matter?







