Amp is the coding agent and development environment that runs anywhere and everywhere.
Joined March 2025
- Tweets373
- Following64
- Followers28.8K
- Likes1.1K
“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….
A thumbs-up on a PR is an alibi: “I'm not really sure, but hey, I got thumbs up from the designer and from two engineers.”
@thorstenball on taking the training wheels off: “if you ship this, it’s live. You can ask for help, but it’s on you.”
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:
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: