Notes on backend engineering, distributed systems, and the occasional detour into mathematics — written as I go, not after the fact.
Case studies from production systems — the problem, the approach, what actually happened after.
Posts that connect to each other over time — this is the part that grows into something bigger.
No fixed schedule here — just an honest, always-current line on what I'm building and learning.
Senior backend developer working on event-driven compliance systems — the kind that watch for money moving somewhere it shouldn't. Most of my day is AWS, Python, and queues that need to never lose a message.
This site is where the rest of it lives: what I'm reading, building on the side, and slowly working out about where I want this career to go.