Why I prefer boring backends and expressive interfaces
I keep reaching for the same backend. Postgres, a handful of tables, a few scheduled jobs, and plain HTTP calls to the services I need to talk to. It is not exciting, and that is the point.
A backend is where I want nothing to surprise me. If a job fails, I want to read one log line and know why. If a table needs a new column, I want to add it without a migration ceremony. Every clever layer I put between the data and the screen is a layer I will be debugging at the worst possible time.
The interface is the opposite. It is where a person spends their time, so it is where I allow myself to be expressive: type that is set carefully, motion that answers what you just did, a page that feels fast because it is fast.
The two projects that show it best
The Seissense ops portal is mostly cron jobs and a database. It has almost nothing to look at, and it is the system people rely on every day. The Vesper lamp page is the reverse: no business logic at all, and a great deal of care in how light falls on a desk.
Both come from the same belief. Put the complexity where it earns its keep, and keep everything else boring enough to forget about.