Form, flow, function
Why an architect's three-word brief became my engineering compass — and why this site looks like a blueprint.
Before I wrote software, I drew buildings. Architecture school teaches you to hold three things in tension at once: form (how it looks and feels), flow (how people move through it), and function (whether it actually works). Drop any one and the building fails — beautiful but useless, useful but joyless, or clever but unlivable.
That brief never left me. It turns out software is the same discipline with a faster feedback loop.
Form
The interface is the building’s facade and its rooms. It sets expectations and shapes how it feels to be inside. Good form isn’t decoration — it’s legibility.
Flow
How does someone move from intent to outcome? In a building that’s circulation; in software it’s the path through a task. Flow is invisible when it’s right and maddening when it’s wrong.
Function
None of it matters if it doesn’t work — reliably, at scale, under load. Function is the structure behind the walls. Unseen, load-bearing, non-negotiable.
This site is my attempt to hold all three at once, drawn as a blueprint because that’s where I learned to.