Amplifying human agency @ampcode Prev: founder @sourcegraph
San Francisco, CA
Joined September 2008
- Tweets7.7K
- Following2.2K
- Followers13.5K
- Likes23.2K
Our orbs, your compute. “Yourbs”
A lot of apps currently feel jank on the iPhone Duo and he estimates it might take 6 months on average to update them to be good.
Somehow I doubt it will take that long in this day and age…
PSA for big enterprises affected by any of today’s security insanity: Sourcegraph provides a way to apply remediations across all your organization’s repositories.
This saved many a Christmas during the log4j incident.
You’ll likely want this for what’s coming.
PHP released patches for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, that could allow attackers to execute code remotely without authentication.
Finding every affected PHP version across hundreds or thousands of repos is a challenge. We're sharing Sourcegraph search queries and Agentic Batch Changes specs to help you find and fix #php2shell vulns.
Learn more: sourcegraph.com/blog/php2she…
Need help? Post a comment and we'll help you get Sourcegraph set up to find potentially affected repos and roll out patches.
Beyang retweeted
If you’re interested in joining, we’re hiring FDEs in Sydney and NYC right now:
ampcode.com/hiring/fde
You can orb from a plane, you can orb on the train.
You can orb from the lab—and even in your Cybercab!
Living in the future!
Was watching @MostlyTechPod in a cybercab, @IanLandsman brought up @AmpCode, realized I should be orbin’ instead
There’s no general web browser in a cab, so I left a comment on YouTube with the amp url which let me open it
It’s orbin’ time
Beyang retweeted
Amp can now (deterministically) Ask First before running certain MCP tools, like transfer_money or send_gmail.
(We talked in ampcode.com/podcast/season-0… how this kind of thing let us trust the agent to do a lot more, like granting credits and emailing users who hit bugs.)
The way we work has to keep up with what the technology is capable of. So much of software development best practices in the past 20 years was founded on axioms that no longer hold.
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:
I'll be speaking at this event organized by @exedev and @jana_iris at @sentry next week to share a bit about what we've found effective when working with agents and maybe some idiosyncratic viewpoints and demos. Hope to see you there!
luma.com/0qr6bxcw?tk=PM7pb4
You can now assign tasks to Amp from Linear!
Very cool to see diffusion models emerging as another model architecture that could shake up the model landscape
A bold experiment
.@vanamerongen is going to lead a pretty wild experiment: turning dev-null.sh into the world’s first agentic social network
the idea: our users open issues directly on the app; those issues get picked up automatically by remote @AmpCode agents running in the cloud.. the agents dig in, propose a pull request, and then self-evaluate their own work.. if the fix is obvious and low-risk (think a small frontend change), it gets merged automatically
no human in the loop! let's see how far we can push it
The Model K was incredibly overpowered. It could do 60mph, insane for those days. But Ford called it a waste of money because what kind of roads would support that kind of speed?
Reminds me of coding agents with legacy codebases and legacy processes.
