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:↗
9 bookmarks
Everything has changed for us with orbs. My biggest struggle right now is figuring out how to make you see what we see. So I sat down and wrote about it: ampcode.com/notes/what-i-w…↗
Friends, it's time to meet Puck. It's a your new assistant in Amp. Fast & always reachable, Puck can: research & read code & check CI, spawn other agents and talk to them, manage all of your threads for you. The agent to manage your agents. ampcode.com/news/meet-puck↗
Read it here: ampcode.com/how-to-pair-wi…↗
Meet Clicky, the browser use subagent in @AmpCode, which records live screencasts with voiceovers of its changes, to prove the correctness of its work to you. Clicky gives Amp another powerful feedback loop to write code better and more autonomously. WIP, will ship when ready.↗
ICYMI -- here's Build Crew Live: Episode 3. Featuring our very own Camden, @thorstenball and @heyneighbor with special guest @mikehostetler↗
Raise you 🤚 if you’re part of the Build Crew in @AmpCode↗
My favorite part about @AmpCode is that you can share your whole session globally. PRs with Amp threads attached make me very, very happy as a maintainer. here is one from a bug fix this morning: ampcode.com/threads/T-24dc…↗