Founder at @triggerdotdev, the OSS AI infra platform. Human in the loop. Team 🇺🇸/🇬🇧. Hiring developers in London and EU
London, UK
Joined March 2019
- Tweets3K
- Following2.3K
- Followers2.6K
- Likes4.5K
Pinned Tweet
we're opening up more roles, hiring remote or in person in London 🇬🇧, building some very cool open source stuff and working on hard/medium/easy problems (we have them all). DM me and please share 🙏
this is what happens when you give @jacksbridger access to your socials
Eric Allam retweeted
7 things we wish we'd known before building our first production chat agent
tgr.dev/ELpr671
👀😏
After a few months surfing in Sri Lanka, playing badminton in Malaysia and living on a farm in Cornwall..
I'm starting a new job tomorrow and it's the most excited I've been for a new job:
- I was a customer of theirs and love the product
- Have been friends with the team for years
- The whole team is really talented and really nice
- I'll be in-person in London
- it's a devtool
They're growing really fast already but my job is gonna be to help increase that slope
pic related: I gatecrashed their offsite in Lisbon last week 😆
One particularly crazy side-quest related to this @PlanetScale migration (and there were many) was tracking down a very obscure bug in PgBouncer, that only reproduced under a very specific set of circumstances:
- prisma client
- using the rust query engine
- with prisma otel turned on (🤯)
- connecting to PlanetScale through one of their dedicated PgBouncer instances on the writer instance, which is the only path that routes through two PgBouncers before hitting the database
It took a couple of days just to track it down. We ended up working around the bug by building a way for us to switch the prisma client to using the pg adapter (which skipped the rust engine for query execution), but only for certain queries (switching everything at once to using the pg adapter was too risky).
Luckily that worked and unlocked the migration. A few days later the reproduction actually led to a PgBouncer fix by an engineer at PlanetScale: (github.com/pgbouncer/pgbounc…)
This summer we upgraded our 56TB Postgres database with (almost) no downtime.
And we moved all new runs to @planetscale Metal.
This post covers everything we did and everything we learned along the way.
tgr.dev/LuKQYce
Eric Allam retweeted
We spent the last 6 months building our take on a chat agent SDK. It’s open source and uses the stateful compute that powers our existing tasks and workflows.
Eric Allam retweeted
Applications for the latest Standard Capital Series A funding cycle are now open!
Apply by July 21, hear back by July 31.
Eric Allam retweeted
On 22-23 June our us-east-1 and eu-central-1 regions had periods of downtime and the overall incident lasted 18 hours.
This falls way short of the reliability we aim for. I’m really sorry to all our customers, who will be receiving credits for that period and more.
What happened, why it took so long to recover, and what we’re changing (starting from yesterday): trigger.dev/blog/incident-re…
Verbal ticks that give away Claude code:
- Blast radius
- Phase 1/2/x
- Smoking gun
- Let me actually check
- Honestly, no
- Honest answer
Eric Allam retweeted
Trigger.dev lets developers add AI agents to their products with a simple SDK, handling execution, long-running workflows, and reliability so they don't have to. Over 90% of their usage now comes from agent workflows, and they recently announced their $16M Series A led by Standard Capital.
In this episode of Founder Firesides, co-founders @mattaitken and @maverickdotdev sat down with YC's @koomen to talk about three versions of the product before finding product market fit, how building async infrastructure for two years accidentally put them in the perfect position for the agent era, and why they think the future of computing is programmatic checkpoint and restore — freezing and resuming compute on demand.
Eric Allam retweeted
Bolto is a single platform that provides AI-native recruiting, HR and payroll in the same product, from YC S23.
I just posted an interview with @mrinalsingh02 and @jakeatbolto, the founders of @boltohq, about their recent $ 12M Series A from @Standard_Cap.
Link below
📝Detailed write up of how we ditched git worktrees in favor of @gitbutler and how we use it with agents here:
trigger.dev/blog/parallel-ag…
Eric Allam retweeted
We led the Series A for Insight Health.
Insight Health builds AI agents for specialty care. The founders include a YC alum, the former head of cloud infrastructure at Twilio, and two practicing physicians.
Welcome to @Standard_Cap, Insight Health!
Eric Allam retweeted
Been running AI automation on GitHub PRs - generating them, reviewing them. Was doing it in GitHub Actions.
Debugging GitHub Actions is a slog. Rerunning a failed job is a hassle. Observability beyond pass and fail requires parsing logs.
Switched to @triggerdotdev. Night and day. Easier to set up, integrate locally, rerun, and actually see what's happening. The DX is much better.
🧵 GitHub webhooks → durable AI tasks, no custom infrastructure.
Here's how we wired the Hookdeck Event Gateway + @triggerdotdev + @claudeai into a production-ready GitHub automation pipeline. 👇
Eric Allam retweeted
Switching from Node to @bunjavascript gave us a 5x speed boost (28x better max latency) but there was a gotcha…
Pending response promises don't resolve on client disconnect. @nodejs handles this automatically. Fix: resolve disconnects with 499.
trigger.dev/blog/firebun
Eric Allam retweeted
Just launched: our Vercel integration for Trigger.
Push code. @vercel deploys your app. @triggerdotdev deploys your tasks. Env vars sync both ways. Your app never goes live with mismatched task versions.
↓
SF is for coding agents, London is for enterprise agents
I have been thinking about where the next wave of AI companies will be built.
If agents start operating inside institutions like finance, insurance, and compliance, London might have an opening.
agent.capital
