I work on backend systems, cloud infrastructure, and applied AI. I write engineering notes here and collect visual explanations of topics I’m learning.
Engineering interests
An architecture diagram can make a system look finished. The interesting questions usually live between its boxes: what happens when a request is retried, a model drifts, or an operator has incomplete information?
That is the kind of engineering I enjoy. Backend design, infrastructure, and applied AI are different ways of approaching the same question: how do we make a complicated thing understandable enough to trust?
How I work
Documentation and interfaces
Names, interfaces, and runbooks are part of the system. A person should be able to form a useful mental model before something goes wrong.
Measurement
Make success measurable, retain the evidence, and leave room for your first explanation to be wrong.
Prototyping
A tiny simulation or visual experiment can answer a question that another hour of reading cannot.
This site
I use this site to work through system designs, publish reproducible notebooks, and test ideas with interactive experiments. Writing the explanation is part of the work.