Amp is the coding agent and development environment that runs anywhere and everywhere.
Joined March 2025
- Tweets369
- Following64
- Followers28.8K
- Likes1.1K
Load has been shedded.
Things should feel better/faster now.
Still trying to get more compute (who isn't?).
Too much love for orbs!
Our database is under heavy load, which is why ampcode.com right now feels very slow or there can be connection issues.
We're on it and investigating.
ampcodestatus.com/
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:
@thorstenball hasn’t written a design doc in three months. When he got stuck on a feature, he asked the agent instead.
Its answer: “Yeah, of course you're stuck, mate.”
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
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:
