Beñat Espiña (@benatespina) header
Beñat Espiña (@benatespina) profile picture

Hands-on engineering manager at Lookiero Outfittery Group: we help stylists dress people. On the side, making event sourcing boring with Bounda.

Bilbao
Joined August 2010
Photo by Beñat Espiña (@benatespina)Photo by Beñat Espiña (@benatespina)Photo by Beñat Espiña (@benatespina)Photo by Beñat Espiña (@benatespina)Photo by Beñat Espiña (@benatespina)Photo by Beñat Espiña (@benatespina)Photo by Beñat Espiña (@benatespina)Photo by Beñat Espiña (@benatespina)Photo by Beñat Espiña (@benatespina)
Your tables keep the last write. Event sourcing keeps every change, but it always looked like a big-platform thing. So I built Bounda, event sourcing and CQRS in TypeScript for the apps most of us build. Open source. Rewind a night at a theatre: demo.bounda.dev
2
2
7
1,302
Event sourcing has a reputation for ceremony: classes, buses, handlers registered by hand. In Bounda a whole feature is two small files. Five things you don't write: aggregate class, registration, types, an exception per no, and the null check you forgot. bounda.dev/blog/a-command-is…
1
31
Every type is generated next to the module. `state` comes from what your events return, `events` only offers this aggregate's events, and `reject` only takes the codes the command declares. `reject("SoldOut")` doesn't compile.
1
25
It borrows the shape from React Router's route modules. The price: names carry weight, so renaming an event is a schema change, not a refactor. Try the rejection in the demo: demo.bounda.dev/?scene=limit
14
What people from engineering keep isn't the code. It's knowing how to break a big problem into small pieces. Years of practice. Most people never had to learn it.
36
How many agents can you run at once? As many as you can verify. Addy Osmani wrote up how the Claude Code team does it. The rule I liked most: a change can't edit the checks that judge it. Review reads its rules from the base branch, not from the PR.
41
Beñat Espiña retweeted
We just launched Shopify Editions Fall 2026 🍁 Here's the technical breakdown of how we built it 🧵
27
46
15
443
41,145
Whoever writes a personal field passes a `string`. Whoever reads it, a fold, a projection, a policy, sees `string | null`. Because one day it will have been forgotten, and the compiler should walk you to every place that assumed it wouldn't.
1
98
If the key sits next to the data, every backup carries both. In Bounda each tenant now gets its own key, kept apart from its database. To forget a whole customer, you destroy one key. The backups stay. They just don't open anymore.
38
Beñat Espiña retweeted
It's an exciting time to invent new frameworks because AI has made the switching cost lower than ever.
10
7
72
6,507
Business and product will never ask for the technical work that pays off most. If engineering doesn't propose it, nobody will.
30
"Software factory" is the new buzzword. It's an agent pipeline pointed at building software. Nothing more. We built one at work. It decides product, not code. The hard part is the same as in any factory: saying exactly what you want, and checking you got it.
1
59
The usual definition: agents plan, code, review and ship with little to no human in the loop. Even there, people still pick the work and say what done means. The spec and the check again. This piece looks at how far most teams are: rdworldonline.com/jellyfish-…
1
30
Ideas in a meeting are cheap. With agents, a working prototype is almost as cheap. So I stopped asking my team for proposals. Build it, then we talk. Arguing over something that runs is a lot shorter than arguing over a slide.
32
The trick is crypto-shredding: one key per person, their fields encrypted with it, forgetting = deleting the key. The part I care about most: a forgotten field reads as `null` in the types, so the compiler finds every place that assumed it was there.
1
66
Love the idea of altitude. Don't ask the agent to fix this crash. Ask it to keep the app crash-free. Yet we still hand agents tickets. A ticket is the size of a person's day, not a model's.
1
70