What I value in software and on the web.

I prefer straightforward tools, durable systems, and interfaces that feel considered instead of decorative. Most problems get better when they are made smaller and named more clearly.

Working style

Clear tradeoffs over vague polish

I like software that exposes its constraints. It is easier to trust, easier to change, and usually faster to debug.

Preferred tools

Small stacks, direct ownership

Plain files, readable code, and setups that do not require a diagram just to explain how they start.

What this site is for

This site is a public notebook as much as a homepage. It collects work that is worth pointing to, writing that is worth revisiting, and enough context for people to understand how I think.

It also stays intentionally light. No build step, no framework, and no unnecessary machinery between an idea and a published page.