Software engineer building and shipping useful software across platforms. I choose the tools that fit the problem, and use agentic development inside a structured engineering workflow.
[5 projects · 8 engineering write-ups]Minimal, drift-free EMOM and Tabata interval timer for Android, with full-screen phase colors legible mid-effort and self-updating release channels outside Google Play.
Portable development toolkit for isolated environments, reusable agent workflows, capability-based installation, and controlled automation across a Linux workstation.
· 6 min read
A production fault leaves one record: what the system wrote down. How to decide what to log, how to shape it, and where the logs go.
· 7 min read
How I use ASD-STE100 as a baseline for technical prose, agent instructions, and project terminology without pretending that ordinary software documentation is strict aerospace STE.
I write each task as a GitHub issue before an agent starts. The issue sets the scope. The repository instructions set the rules.
An agent can write the research, the code, and the tests. The task usually ends as a pull request. I run the same checks before each merge. If I ask for a review, I wait for that review. The documents record the decision. The next session starts from the repository.
Get in touch