
building at @warpdotdev, prev: @microsoft β’ dream big and follow through even bigger
Joined July 2013
- Tweets14.4K
- Following539
- Followers22.7K
- Likes9.2K
Safia π©πΎβπ» retweeted
I built the custom webhooks feature in Warp and set up the self-improvement loop with Sentry errors -> fixes within Warp π
Check out this article to see what else we're doing for self-improvement!
best part of @diabrowser is that it romanticizes being up at 4:31am
What's the fastest way to get a hold of good support at Meta these days?
A small business I care about deeply is dealing with their Facebook page being taken over and is trying to figure out ways to remediate.
Got to spend some time back in the Azure Portal while building this out...very nostalgic!
Check it out -- I'm particularly happy with the automations support we landed here.
Warp is one of the few (only?) cloud agent platforms that lets you integrate with ADO's events so easily.
Moving to a model where engineers can "self-stamp" PRs authored by agents they initiated is an easy way to reduce the code review burden on a team.
It also progresses nicely to the model where agents are fired autonomously to make code changes in reaction to bug reports/crashes/etc. instead of human intent.
I sat down with @clairevo to talk about how we're automating development at Warp.
One big change is how we approach code review - for low risk changes, we now let engineers review agent PRs and ship themselves, rather than requiring a second devβs review.
Safia π©πΎβπ» retweeted
We are investing more and more into tooling to understand and optimize our coding agents like benchmarks, agent tracing, etc to figure out why are they spending so much, how to increase prompt adherence etc. It's the next gen of "devtools."
it's interesting because we are also investing at the same time in ways to get agents to use the old generation of devtools (e.g. profilers, debuggers, chrome devtools) that humans used to use to debug code
we just keep going up in abstraction layers but it's the same stuff
Safia π©πΎβπ» retweeted
Introducing Factory Benchmarks: The first model bench generated from your own coding tasks.
Measure, test and improve coding agents by replaying past agent runs, and cut cost-per-PR by 63%+
Hereβs how it works π§΅
I'll be speaking at @kc_dc next week -- reprising my "building a web framework from scratch" talk for the last time.
It's 1-hour of AI-free, slide-free, live-coding where I start with a HTTP server and build out the core components of an API framework in C#.
End of an era π₯²
Safia π©πΎβπ» retweeted
We see everyday how much the @warpdotdev team cares.
But what was special to me here was being able to help @warpdotdev build faster, and then help Warp's customers build faster too.
Warp started by building the terminal every developer loves. Today, their products reach 51% of the Fortune 500.
Now Warp uses Namespace to build more, faster. With Namespace, they've 4x'd their CI performance and now run 20,000+ sandboxes a month for their cloud agent platform.
We went to NYC to sit down with Aloke, Head of Product Engineering at Warp, to get the full story.
My entire day was riding on being able to get quesabirria tacos from my favorite truck tonight but they canceled so I'm not sure what to live for now
Giving things cute names is like 80% of the fun.
Replying to @vyedin
@captainsafia is the queen of this, her dotnet version manager was called dotty and i loved it
Hoooooonessssttttlllyyyyy....I feel like a crazy person sometimes talking to 593285 different agents on Slack π
We've been working on beefing up our cloud agents abilities to debug our production systems and the results are phenomenal.
I'm GEEKED right now watching a @warpdotdev cloud agent root-cause a container startup issue using logs and metrics across our entire infra.
I was trying to get clarity on something with Fable 5 and it found a supporting doc that was drafted in a branch (that didn't have a PR) in another repo to give me an answer.
Very impressive!
Iβm running for President on the platform that you canβt show previews for horror movies before non-horror movies.
Safia π©πΎβπ» retweeted
The speed at which a product is developed doesn't inherently make the product better or worse. The number of commits doesn't make the product better or worse. The number of people or agents working on it doesn't make it better or worse. The number of hours youβre pouring into it doesnβt make it better or worse. Working on a weekend, or late into the evening, doesnβt make it better or worse. Talking about these things sounds like itβs talking about the product, but itβs not talking about the product.
Those are all development metrics and styles of work. They don't speak to the product itself. They're all back of the house. Important to those making the work, but not inherently important to the people using the work.
Development metrics and style say nothing about fit. They say nothing about quality. They say nothing about clarity. They say nothing about usability. They say nothing about utility. They say nothing about performance. They say nothing about how customers feel when they use your product.
It's like reviewing a restaurant by talking about how many cooks were in the kitchen, how long the shift lasted, how many orders they fired, or how late they stayed cleaning up. None of that tells you about the meal, the product, the customerβs experience.
Mistaking making for the thing you've made is like confusing the kitchen for the meal or the blueprint for the building. They're connected, but they're not the same thing. One of them matters a whole lot more than the other.













