Amp is the coding agent and development environment that runs anywhere and everywhere.
Joined March 2025
- Tweets393
- Following64
- Followers29.6K
- Likes1.1K
“Imagine you could snap your finger and working with data would be now your dream setup.”
@thorstenball: with agents, you can finally build the tooling you used to brush off.
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:
“How do you not ship slop if everybody can just push to main?”
@sqs and @thorstenball answer the replies to The Company of the Future, and explain how Culture Stops Slop.
00:00 Intro: Tough luck, get the tokens
01:08 The responses to The Company of the Future
02:06 Don't meet people where they are
03:45 Self-hosted Orbs: a big architecture change without an RFC
09:16 Adapters are cheap now: customers fill in the last 20%
12:51 "You're only 21 people" is the point
15:58 Do what gives you energy & Quinn's secret Android app
20:44 macOS Satellites & capital-A Agile
27:21 A feature's whole life in one thread
29:26 Culture stops slop
33:21 No PMs in the middle & adopting a customer
36:54 Avoiding the everything app & not hiring your way out
40:43 A shared sense of urgency & removing features
46:29 "Why believe you?" You've got it backwards
48:29 Unit tests vs proof: videos & screenshots
53:53 The real cost of code review
58:17 Get to the tokens
You can also watch it on YouTube: youtu.be/tEse6n4hEJQ
Or listen to it on Spotify: open.spotify.com/show/1AL44J…
If you want to listen to all of them: ampcode.com/podcast
Amp’s one weekly meeting ends in silence: everybody writes down their goals for the week.
@thorstenball on aiming high when everyone can see what you wrote last week.
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 could take any person on the team and drop them in front of our most important customer and we would feel safe.” — @thorstenball
Plus @sqs on the unscheduled talk at a big bank that left him “serenely happy.”
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:
A user reports a bug. Amp waits for the fix to roll out, then emails them: the fix is live, and here’s $10 in free credits.
Then it finds everyone else who hit the bug and emails them too. — @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:
Amp retweeted
Time to ask Amp to visualize things.
Charts, timelines, diagrams, mockups: Amp can now build things for you right in the the thread.
ampcode.com/news/visualize-t…
Code review, other teams, schedules: “it's easy to tell yourself, well, no, that’s just how companies work.”
@sqs on why zero friction beats a little friction.
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
Amp now has macOS Satellites!
Agents can now spawn Macs and build, test and run your iOS and macOS applications on them.
Rolling out now.
ampcode.com/news/macos-satel…
At Amp, the story behind a change lives in the thread, legible to humans and agents, and richer than any commit message or AI-generated PR description.
@thorstenball and @sqs: “the human intent is in the Amp thread.”
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:
One of Amp’s principles: do what gives you energy.
“It sounds like super woo-woo, but if something gives you energy, you’re going to do it way better.” — @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:
Before @sqs changes a feature, he has the agent add logging, ships just that, and lets it watch for an hour or a day.
“If I had to wait for another person to go and review that PR, that would slow me down.”
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:
In a traditional company, an idea goes designer → Figma → PM → engineer → “is this worth the effort?”
At Amp, someone tries it first and asks “should we ship this?” If the answer is “no”, it was just a prompt, not two weeks of work.
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:
After an incident, finding every affected user and emailing them used to be a day of scripts and log searches.
Now you ask Amp. @thorstenball: “with agents, you can do stuff that was previously unreasonable.”
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 don't have quarterly goals. We don't have annual goals.”
The closest thing Amp has to a roadmap is February's “The Coding Agent Is Dead”. @thorstenball: “that was like maybe a roadmap for the year, but it wasn’t prompted by a fiscal quarter.”
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 don't need the people that are just turning their brains off asking for sizing points in a Jira ticket.”
@sqs and @thorstenball on what changes when hiring isn’t the answer to every problem.
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
Amp now supports BYOK through Microsoft Foundry, formerly known as Azure AI Foundry, formerly known as Azure AI Studio.
Set it up at ampcode.com/settings/model-r….
