These are the kinds of problems I like: real people, real constraints,
and enough moving parts that you have to think in systems, not just screens.
Home & family
HomeCloud
Private family portal · Files · Notes · Shared utilities
A small web app I built for my own world. HomeCloud replaces scattered
drives, random text threads, and “where did we put that” conversations
with one calm place to put important stuff.
- Role-based access for admin / family / guests.
- Simple left-nav for files, notes, quick links, and Wi-Fi info.
- Soft activity history – enough context without feeling like tracking.
- Designed to feel obvious to non-technical people in the house.
It’s a living project: layout and flows evolve as we actually use it.
A lot of my thinking about “calm systems” started here.
Network tool
NetLapse
Network snapshot · Scan · Identify · Document
NetLapse is my “what’s really on this network?” tool — built for fast visibility.
It focuses on clean output, readable status, and capturing a snapshot that you can
actually use (instead of a wall of noise).
- Quick discovery scan with clear device rows (not clutter).
- Details view that surfaces the useful bits first.
- Designed to support real troubleshooting workflows.
- Built with a “status-first” mindset: what changed, what matters, what’s next.
It’s the kind of tool I wish every environment had by default: fast, quiet, and obvious.
Work context
Internal tools & workflows
Tech-facing · People-first
I gravitate toward tools that sit between people and hardware:
dashboards, small utilities, and views that make complex setups
feel predictable.
- Mapping how information moves before deciding what to build.
- Flattening complicated flows into one or two clear screens.
- Favoring naming and structure over flashy UI tricks.
- Designing for the person who just wants it to “work every time.”
These projects aren’t always public-facing, but they shape how I
approach any system: clarity, repeatability, and low friction.
Next
Future builds
Always in draft
I keep a running list of systems I want to build or refine next:
better ways to surface status, calmer ways to onboard people into
complex setups, and tools that quietly prevent problems.
- Lightweight “ops” views for everyday environments.
- Smarter defaults for recurring tasks and routines.
- Bridging the gap between physical hardware and web-based tools.
If you have a system that’s technically “working” but feels heavy,
that’s usually where I’m the most useful.
