I build delightful software with sharp systems and soft edges.
I’m Alex, a software engineer who likes opinionated architecture, obsessive UI polish, and writing code that future-me won’t hate.
I build like an editor.
Make it readable.
Make it feel right.
The work is rhythm and boundaries. It is the small decisions that keep a product calm, legible, and kind to the next engineer.
- 01 · SCOPEShip everything.Ship the smallest honest version.
- 02 · ARCHITECTUREBe clever.Be obvious and stable.
- 03 · INTERFACESIt works.It feels considered.
- 04 · RELIABILITYHandle it later.Do the edge cases now.
- 05 · CRAFTGood enough.Clean, consistent, then shipped.
A playlist, not a gallery.
Here are a few things I build, described like tracks because it’s more fun (and more honest).
An internal forestry management platform that brings planning, suppliers, maps, and reporting into one place.
Forestry projects span locations, stakeholders, timelines, and costs. When the source of truth is spreadsheets, email threads, and documents, teams lose time and confidence in the data.
A unified web app with data-dense workflows: project tracking, supplier orders tied to cost allocation, interactive mapping, reminders, and reporting dashboards.
- Centralized modules for projects, stakeholders, and operations
- Supplier and order management with project-linked cost attribution
- Interactive mapping and location tooling (Google Maps API)
- Reporting with dashboards and cost breakdowns
- Typed full-stack approach with validated server actions
The stack I reach for (and why)
Most people don’t care what tools you use. They care if the product feels good. Here’s how my brain tends to operate.
- prefer boring architecture over cleverness
- slice features thin and deliver daily
- type boundaries so refactors stay friendly
- instrument the happy path and the sad path
- make the empty state feel intentional
If you’re hiring, collaborating, or just want to talk shop, I’m reachable.
Best channel: email. Bonus points if you include your favorite color.