Escritos.
Notas extensas sobre arquitectura, eventos y criterio.
6 ensayos
Sagas vs Temporal: where I actually land
Both solve orchestration. They ask you to pay in different currencies — operational surface, cognitive load, vendor gravity. Here's the ledger I keep.
Bounded contexts are a people problem
The hardest part of domain-driven design was never the aggregates. It's admitting where one team's language ends and another's begins.
When I reach for Go next to a Symfony core
Not everything wants to live in the monolith. A short field guide to the seams where a small Go service earns its keep.
AI features that survive contact with users
The demo is easy. The system that keeps its promises at 2am under real traffic is the whole job.
Writing systems that outlast their authors
Code is a liability you're renting to the future. Some notes on lowering the rent.