Systems people touch every day
PCs, AV, networked gear, and the control surfaces on top of them. I like when the tech fades into the background and what’s left is just “this works.”
Personal site · v2.7
I build and debug systems so people don’t have to think about them.
This isn’t a full portfolio, more a signal: how I think, what I pay attention to, and the kinds of problems I keep saying yes to. If there’s tech involved, real people using it, and room for things to go wrong, I’m interested.
What I do
- • Make messy setups feel predictable and understandable.
- • Design flows for people who don’t have time for tutorials.
- • Keep long-term maintenance in mind from the start.
How I think
- • Start from real constraints, not fantasy features.
- • Map the system, then fix the right part of it.
- • Favor clarity over cleverness; honest over flashy.
System updates
What changed recently
Loading updates…
What I like to build
Not every project, just the patterns
Dashboards, tools, internal portals
Simple interfaces where someone can glance, decide, and move on. Less dashboard-as-art, more “I know what to do in five seconds.”
The space between systems
The handoff between tools matters. I pay attention to how information travels, who needs to see it, and how we keep it from getting lost.
Spotlight project
HomeCloud
HomeCloud is my answer to the “messy shared drive” problem – a small, opinionated web app for my own world. It’s built as a private family portal where everything important has a place and a clear owner.
- Role-based access: simple roles for “admin”, “family”, and “guest”.
- Clean left-side navigation: files, shared notes, quick links, and more.
- Upload and organize: a home for documents, PDFs, and reference files.
- Activity awareness: who added what, and when (without feeling like surveillance).
- Shared utility space: things like Wi-Fi details, how-tos, and little checklists.
It’s not meant to be a product – it’s a living tool. I keep refining the layout and flows as my family actually uses it, and a lot of that thinking shows up in how I approach other systems too.
Systems map
Tap a node to see how I think about that part of the system.
People first. The whole point of the system is to
make real people’s lives easier. If they’re confused or frustrated,
the system is wrong – even if the diagram says it’s “correct.”
Timeline, loosely
How I ended up thinking this way
First phase
PCs, games, and trial-and-error
Learning by breaking things and fixing them again. Hardware limits made me pay attention to how everything fit together.
Team environments
Tech that other people rely on
Working with people who don’t care about the tech itself – they just need it to do its job. Clarity and reliability suddenly mattered a lot more.
Current phase
Structure + experimentation
Mixing real-world systems with digital tools, trying to keep both grounded and flexible. Less show, more signal.
What I’m focused on now
A /now section instead of a slogan
This section exists so the page can change as I do. Right now, the main threads look like:
- • Sharpening how I explain systems to non-technical people.
- • Building small tools that quietly save time every day.
- • Paying attention to how tech actually feels to use, not just how it works.
Last updated: Month YYYY