Current focus
Reducing alert noise without losing the signal.
Three weeks into pruning a runbook nobody read. The interesting question is which alerts deserve a name, not which ones we can mute.
Engineering log · 2026·04
I'm a software engineer who'd rather show the trail than the trophy. This site is a small, dated log of work, decisions, and the lessons that earned their place. Read it like a notebook — slowly, and out of order if you like.
// now
Current focus
Three weeks into pruning a runbook nobody read. The interesting question is which alerts deserve a name, not which ones we can mute.
Quietly learning
Reading Naur and Hancock back-to-back. Not because I'll write any of it — because the framing helps when the team's mental model drifts.
Bench
`decide` writes a one-page ADR-style note, links it to the change, and leaves a breadcrumb that survives the team. Mostly for me. So far.
// log
Plain notes. Unfinished welcome.
One sentence that shows up in the list and in previews.
// decisions
A small archive of thinking I'd like to keep honest.
One sentence naming the tradeoff — what you picked and what you gave up.
// field notes
Migrated from dev.to and reflectoring.io · kept for the record.
Generate OpenAPI documentation from Spring Boot code using Springdoc — a fast path from running endpoints to a published Swagger UI.
Specify the API before writing code, then generate Spring Boot interfaces and models from the OpenAPI document with the OpenAPI Maven plugin.
A short tour of Spring Data R2DBC and a reactive REST API in Kotlin — non-blocking access to a relational database with Spring Boot 2.2.
// channels
Best for slower conversations and longer threads.
Roles, references, and the timeline this site won't keep.
Open notebooks and small tools, mostly works in progress.