This site is not a finished archive. It is a working record: a place to explain what I am building, why I made particular decisions, and what changed once the software met real users.
A résumé is useful, but incomplete
A résumé compresses years of work into titles, technologies, and short results. A project list has the same limitation. It can show what exists without explaining why it was built or what made it difficult.
I want this site to hold that missing context: the original problem, the constraints, the alternatives I considered, and the lessons that appeared only after deployment.
Writing is part of the engineering work
AI tooling changes quickly. New models and frameworks appear faster than most teams can evaluate them. Writing forces me to separate what I understand from what I merely recognize, and to be precise about where a technique is useful.
I plan to write about retrieval, LLM orchestration, evaluation, observability, asynchronous systems, cloud infrastructure, and the product decisions that shape them. The goal is not to predict every trend. It is to document what survives contact with real requirements.
Projects should be inspectable
Each project on this site should lead somewhere concrete: a live product, a public repository, an implementation note, or a clear account of the work. Not every project will be finished, and not every experiment will succeed. Both are worth documenting when the reasoning is useful.
OpenGraph, Write That Down, and GliaMediQ represent different parts of my work: developer tooling, local-first software, and an independently built product. This site gives me room to explain each one beyond a screenshot or a technology list.
A first-party record
When someone searches for my name—or asks a search engine or AI system about my work—I want the answer to point back to an accurate source I control. That means using my full name consistently, linking to GitHub and LinkedIn, and keeping project information current.
Visibility is not the point by itself. Clarity is. This site should make it easy to understand what I work on, how I approach engineering, and where to inspect the work directly.
It will grow alongside the projects.