Tiarê Balbi Bonamini
What you learn today is gone tomorrow. I write to make it last — turning study notes and hard-won lessons into articulated posts about software, technology, and the craft of building things.
I've been writing software since 2008 — from Java monoliths to distributed systems, from São Paulo to Vancouver. I'm a Brazilian engineer living in Canada who believes the best way to learn is to build, and the best way to retain is to write.
I maintain a personal tech radar to organize what I'm exploring, and this site is where those explorations become something more permanent. Every post starts as rough study notes and evolves into something I'd want to read myself.
A 0-click query for `dbos ontime` showed up in my Search Console last week. The reader is not asking about DBOS — they are asking how to run a job every minute, exactly once, across a fleet. From my own notes, an etcd lease, the `concurrency.Election` package, and a fencing token cover that case in under 100 lines of Go, without pulling in a workflow engine.
When the log is the source of truth, every schema change is permanent. A Kotlin/Avro walkthrough of the rename that passed the Schema Registry check and silently corrupted every old event, plus the Protobuf and Avro invariants I now keep pinned above my desk.
Notes from two weekends of digging into DSPy. I stopped treating prompts as the source of truth and started treating them as compiled output from a typed signature, a metric, and an optimizer. Here is the smallest end-to-end program I kept, how MIPROv2 actually searches, and where the approach breaks down in practice.
Spring AI's server-side A2A integration is stable enough to put in production, but the protocol is most useful at organizational boundaries, not as an internal RPC replacement. This post walks through what actually changes in a Spring AI codebase, where the sharp edges still are, and a practical decision framework for A2A vs MCP vs plain REST.