Eric Allam

Trigger.dev

@maverickdotdev

Founder at @triggerdotdev, the OSS AI infra platform. Human in the loop. Team 🇺🇸/🇬🇧. Hiring developers in London and EU

London, UK trigger.dev Joined March 2019

2.3K Following 2.6K Followers 3K Posts

Latest posts 5

Pinned post

Eric Allam @maverickdotdev Sep 30, 2025

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 🙏

Trigger.dev Verified account @triggerdotdev Sep 30, 2025

Considering a new job role 👀? We've just opened up new engineering positions and would love to hear from you if you are a:

→ Support Engineer
→ Senior Backend Engineer

Apply below ↓

View quoted post on X

Eric Allam @maverickdotdev Oct 26

Our number 1 feature request is out now: Webhooks is now in public beta. Your webhooks, now even more durabler (durablish?)

1:18

Trigger.dev Verified account @triggerdotdev Oct 26

Introducing Webhooks to Trigger: now you can build AI agents on top of the services your customers already use, like Stripe, Supabase and Slack.
tgr.dev/webhooks-x
View quoted post on X

Eric Allam @maverickdotdev Oct 16

this is what happens when you give @jacksbridger access to your socials

Trigger.dev Verified account @triggerdotdev Oct 16

Happy Friday

View quoted post on X

Eric Allam @maverickdotdev Sep 30

👀😏

Jack Bridger Verified account @jacksbridger Sep 30

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 😆

View quoted post on X

Eric Allam @maverickdotdev Sep 30

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/pgbo…)

github.com Fix prepared-statement response ordering for batched Close by mble · Pull Request #1555 · pgbounc... Faults PgBouncer can send prepared-statement responses in the wrong order when a batch mixes Parse and Close without an intervening Sync. There are two related faults. Fake response after a skipped...

Trigger.dev Verified account @triggerdotdev Sep 30

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
View quoted post on X