Amp is the coding agent and development environment that runs anywhere and everywhere.
amp-devs@ampcode.com
- Tweets 337
- Following 64
- Followers 26,567
- Likes 1,130
"Just use a cheaper model" sounds like saving money.
But fiber didn't just make your internet faster. It made whole new businesses possible. @thorstenball and @sqs discuss how the same is true with frontier models.
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?
1
6
43
14,632
You can also watch it on YouTube: piped.video/3v7dIHh15dk
Or listen to it on Spotify: open.spotify.com/show/1AL44J…
If you want to listen to all of them: ampcode.com/podcast
3
1,492
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?
6
6
55
48,914
@sqs and @thorsten on the decay of the local dev env:
"We found this with the shift to orbs, when as soon as you started making the Orb environment good, that's all people ever wanted to use."
What is the computer for now?
In Raising an Agent S2E4, @sqs and @thorstenball explore how agents can do more than just ship code, discuss recent outages, and ask what happens to our computers when more work moves into Orbs.
00:00 Intro: What is the computer for now?
01:32 New models & aiming higher with agents
04:42 An agent's job after the code ships
10:19 Mini evals & keeping the team's context in threads
13:38 Performance testing & production canaries
18:36 Amp's recent outages & what went wrong
24:44 Shipping faster & the tradeoffs of redundancy
28:34 How fast can an engineering team go?
32:27 Making production logs & metrics useful to agents
37:15 Beyond local development
41:30 Agents building 3D models & virtual worlds
43:35 Simpler devices & dictating work on the go
47:29 What happens to the tools we love?
49:27 Steering, queuing & changing workflows
6
16
9,192
@sqs on the advantage of using a single coding agent across the whole org:
"All of our intent, all of our history, is in Amp, in threads, in something that's legible to the agent."
"You can see why this was added here, and you don't just get the commit message, you also get everything the human said to get it there."
"If you are a company that's using seven different agents... I understand why a lot of companies do that, that might be a reality, but you are going to lose out on a lot of Agent Power if you do not have all of that context accessible to the agent."
What is the computer for now?
In Raising an Agent S2E4, @sqs and @thorstenball explore how agents can do more than just ship code, discuss recent outages, and ask what happens to our computers when more work moves into Orbs.
00:00 Intro: What is the computer for now?
01:32 New models & aiming higher with agents
04:42 An agent's job after the code ships
10:19 Mini evals & keeping the team's context in threads
13:38 Performance testing & production canaries
18:36 Amp's recent outages & what went wrong
24:44 Shipping faster & the tradeoffs of redundancy
28:34 How fast can an engineering team go?
32:27 Making production logs & metrics useful to agents
37:15 Beyond local development
41:30 Agents building 3D models & virtual worlds
43:35 Simpler devices & dictating work on the go
47:29 What happens to the tools we love?
49:27 Steering, queuing & changing workflows
3
2
44
8,153
"I'm just pointing at things and saying, make it like this and ship this and do this. The altitude is so high. It's wild. Even compared to two months ago."
@thorstenball on using agents for the whole lifecycle of a feature: building, testing, shipping, monitoring the rollout, toggling feature flags, talking to users.
What is the computer for now?
In Raising an Agent S2E4, @sqs and @thorstenball explore how agents can do more than just ship code, discuss recent outages, and ask what happens to our computers when more work moves into Orbs.
00:00 Intro: What is the computer for now?
01:32 New models & aiming higher with agents
04:42 An agent's job after the code ships
10:19 Mini evals & keeping the team's context in threads
13:38 Performance testing & production canaries
18:36 Amp's recent outages & what went wrong
24:44 Shipping faster & the tradeoffs of redundancy
28:34 How fast can an engineering team go?
32:27 Making production logs & metrics useful to agents
37:15 Beyond local development
41:30 Agents building 3D models & virtual worlds
43:35 Simpler devices & dictating work on the go
47:29 What happens to the tools we love?
49:27 Steering, queuing & changing workflows
7
4
42
37,693
What is the computer for now?
In Raising an Agent S2E4, @sqs and @thorstenball explore how agents can do more than just ship code, discuss recent outages, and ask what happens to our computers when more work moves into Orbs.
00:00 Intro: What is the computer for now?
01:32 New models & aiming higher with agents
04:42 An agent's job after the code ships
10:19 Mini evals & keeping the team's context in threads
13:38 Performance testing & production canaries
18:36 Amp's recent outages & what went wrong
24:44 Shipping faster & the tradeoffs of redundancy
28:34 How fast can an engineering team go?
32:27 Making production logs & metrics useful to agents
37:15 Beyond local development
41:30 Agents building 3D models & virtual worlds
43:35 Simpler devices & dictating work on the go
47:29 What happens to the tools we love?
49:27 Steering, queuing & changing workflows
6
7
64
141,408
"I could just replace that with EC2 and some shell scripts and get the same thing."
But could you?
Thoughts and question of when to build and when to buy.
And @sqs putting @thorstenball fully on the spot by asking him whether people should build their own Amp or not.
4
5
35
7,464
@thorstenball's pet theory on why engineers are so busy tweaking skills and tools and workflows:
"Because it can't be that easy, right?"
Raising an Agent, S2E3: When Tokens Flow Like Electricity.
@sqs and @thorstenball on what happens when intelligence gets cheap: build vs. buy flips, why everyone building software to build software to do X is probably incorrect, and when software starts to feel like owning a house instead of renting one.
00:00 Intro: Cheap intelligence & doing X instead of building software to do X
01:06 Back home after Munich & what's changed in how we build
02:06 Predictions: the price of intelligence drops, tokens flow like electricity
05:54 Everyone is building dev tools & why that's the wrong bet
06:57 Pet theory: engineers can't believe it's this easy
10:33 Orbs vs. EC2, a VPN & tmux
17:18 Build vs. buy when the models keep changing
20:14 If Amp is worth buying, why isn't an issue tracker?
27:34 Killing features & vibe coding the 2% of a SaaS product you need
30:03 Build on a solid core: glue code is the worst part
33:19 The two Amps: jellyware, homeowners & renters
37:01 Exporting the Amp way to more teams
43:42 Opinionated software from people you trust
5
4
45
10,109
Quinn on everyone now building developer tooling:
"Just building software to do X is only valuable if you can get people to pay and I think that's going to be a lot harder."
Raising an Agent, S2E3: When Tokens Flow Like Electricity.
@sqs and @thorstenball on what happens when intelligence gets cheap: build vs. buy flips, why everyone building software to build software to do X is probably incorrect, and when software starts to feel like owning a house instead of renting one.
00:00 Intro: Cheap intelligence & doing X instead of building software to do X
01:06 Back home after Munich & what's changed in how we build
02:06 Predictions: the price of intelligence drops, tokens flow like electricity
05:54 Everyone is building dev tools & why that's the wrong bet
06:57 Pet theory: engineers can't believe it's this easy
10:33 Orbs vs. EC2, a VPN & tmux
17:18 Build vs. buy when the models keep changing
20:14 If Amp is worth buying, why isn't an issue tracker?
27:34 Killing features & vibe coding the 2% of a SaaS product you need
30:03 Build on a solid core: glue code is the worst part
33:19 The two Amps: jellyware, homeowners & renters
37:01 Exporting the Amp way to more teams
43:42 Opinionated software from people you trust
6
1
44
407,231
We're investigating an infrastructure failure that causes large parts of ampcode.com being unavailable.
Sorry about that. We'll keep you updated on ampcodestatus.com/.
15
2
92
10,229
What can United Airlines teach Anthropic and OpenAI about pricing?
Or, what does flying economy have to do with token subsidies?
Raising an Agent, S2E3: When Tokens Flow Like Electricity.
@sqs and @thorstenball on what happens when intelligence gets cheap: build vs. buy flips, why everyone building software to build software to do X is probably incorrect, and when software starts to feel like owning a house instead of renting one.
00:00 Intro: Cheap intelligence & doing X instead of building software to do X
01:06 Back home after Munich & what's changed in how we build
02:06 Predictions: the price of intelligence drops, tokens flow like electricity
05:54 Everyone is building dev tools & why that's the wrong bet
06:57 Pet theory: engineers can't believe it's this easy
10:33 Orbs vs. EC2, a VPN & tmux
17:18 Build vs. buy when the models keep changing
20:14 If Amp is worth buying, why isn't an issue tracker?
27:34 Killing features & vibe coding the 2% of a SaaS product you need
30:03 Build on a solid core: glue code is the worst part
33:19 The two Amps: jellyware, homeowners & renters
37:01 Exporting the Amp way to more teams
43:42 Opinionated software from people you trust
3
2
20
31,393
Is vibe coding fun?
Or does it take away the funnest parts of programming and leave you with the rest?
Raising an Agent, S2E3: When Tokens Flow Like Electricity.
@sqs and @thorstenball on what happens when intelligence gets cheap: build vs. buy flips, why everyone building software to build software to do X is probably incorrect, and when software starts to feel like owning a house instead of renting one.
00:00 Intro: Cheap intelligence & doing X instead of building software to do X
01:06 Back home after Munich & what's changed in how we build
02:06 Predictions: the price of intelligence drops, tokens flow like electricity
05:54 Everyone is building dev tools & why that's the wrong bet
06:57 Pet theory: engineers can't believe it's this easy
10:33 Orbs vs. EC2, a VPN & tmux
17:18 Build vs. buy when the models keep changing
20:14 If Amp is worth buying, why isn't an issue tracker?
27:34 Killing features & vibe coding the 2% of a SaaS product you need
30:03 Build on a solid core: glue code is the worst part
33:19 The two Amps: jellyware, homeowners & renters
37:01 Exporting the Amp way to more teams
43:42 Opinionated software from people you trust
9
3
30
21,201
You can also watch it on YouTube: piped.video/SI3N8MCQHfo
Or listen to it on Spotify: open.spotify.com/show/1AL44J…
If you want to listen to all of them: ampcode.com/podcast
6
5,588
Raising an Agent, S2E3: When Tokens Flow Like Electricity.
@sqs and @thorstenball on what happens when intelligence gets cheap: build vs. buy flips, why everyone building software to build software to do X is probably incorrect, and when software starts to feel like owning a house instead of renting one.
00:00 Intro: Cheap intelligence & doing X instead of building software to do X
01:06 Back home after Munich & what's changed in how we build
02:06 Predictions: the price of intelligence drops, tokens flow like electricity
05:54 Everyone is building dev tools & why that's the wrong bet
06:57 Pet theory: engineers can't believe it's this easy
10:33 Orbs vs. EC2, a VPN & tmux
17:18 Build vs. buy when the models keep changing
20:14 If Amp is worth buying, why isn't an issue tracker?
27:34 Killing features & vibe coding the 2% of a SaaS product you need
30:03 Build on a solid core: glue code is the worst part
33:19 The two Amps: jellyware, homeowners & renters
37:01 Exporting the Amp way to more teams
43:42 Opinionated software from people you trust
5
8
59
596,873
Do you still need to read every line of code?
Or are there faster ways, even if you want to be 100% confident about a code change?
Episode 2 of Raising an Agent Season 2: Orbs and Jellyware.
@sqs and @thorstenball recorded this one together in person in Munich last week, where the whole Amp team had gathered for a week of building.
They discuss why isolated Orbs make it easier to run agents in parallel, how the team asks agents for exhaustive verification, and how production itself can become a feedback loop.
They also discuss jellyware: high-quality software that is designed to change quickly. When agents make software more malleable, teams can fix bugs faster and raise the quality bar instead of lowering it.
00:00 Intro: Agents in Orbs & production feedback loops
01:17 Recording together in Munich & what shipped since episode 1
03:56 How the Amp team adopted Orbs
07:00 Giving agents safe production access
11:01 Zero-friction threads & the limits of local checkouts
13:02 Asking agents for 100% proof
18:54 Production as a feedback loop
22:15 Multiplayer & agents as collaborative tools
24:13 Design workflows with Portals
27:27 High-quality software beyond vibe coding
31:17 How code review changes when agents write the code
35:26 Dictation & getting better context into agents
39:08 Jellyware: high-quality software that changes fast
42:27 Faster bug fixes, feedback & the quality budget
49:34 What Amp shipped: subscriptions, Puck, and agent communication
51:42 Automations, polling, and webhooks
1
1
20
14,270
What changes when each agent gets its own disposable computer?
For us, turns out a lot.
Episode 2 of Raising an Agent Season 2: Orbs and Jellyware.
@sqs and @thorstenball recorded this one together in person in Munich last week, where the whole Amp team had gathered for a week of building.
They discuss why isolated Orbs make it easier to run agents in parallel, how the team asks agents for exhaustive verification, and how production itself can become a feedback loop.
They also discuss jellyware: high-quality software that is designed to change quickly. When agents make software more malleable, teams can fix bugs faster and raise the quality bar instead of lowering it.
00:00 Intro: Agents in Orbs & production feedback loops
01:17 Recording together in Munich & what shipped since episode 1
03:56 How the Amp team adopted Orbs
07:00 Giving agents safe production access
11:01 Zero-friction threads & the limits of local checkouts
13:02 Asking agents for 100% proof
18:54 Production as a feedback loop
22:15 Multiplayer & agents as collaborative tools
24:13 Design workflows with Portals
27:27 High-quality software beyond vibe coding
31:17 How code review changes when agents write the code
35:26 Dictation & getting better context into agents
39:08 Jellyware: high-quality software that changes fast
42:27 Faster bug fixes, feedback & the quality budget
49:34 What Amp shipped: subscriptions, Puck, and agent communication
51:42 Automations, polling, and webhooks
1
2
23
16,031