About
I like engineering that still makes sense when you zoom in.
I like software with edges: systems work that has to stay reliable, data-heavy applications that need restraint, and infrastructure experiments that are still grounded in day-to-day use.
The common thread is not one specific framework or platform. It is the kind of problem where the internals matter: where a clean interface still depends on disciplined backend behavior, where the network is part of the product, or where automation needs to be trustworthy enough to disappear into the background.
I am especially drawn to the overlap between systems thinking and everyday usefulness. Router firmware, home automation controllers, service design, and hybrid applications all live in different layers of the stack, but they reward the same habits: careful modeling, realistic failure assumptions, and a bias toward clarity over ceremony.
Systems and data
Low-level thinking, careful performance tradeoffs, and software that stays understandable under load.
Networks and firmware
Customizing open-source router operating systems and treating the home network like a living engineering project.
Home automation
Building controllers and flows that feel dependable instead of “smart” in the annoying sense.
Hybrid and web apps
Shipping product surfaces that connect clean UI decisions to solid backend behavior.
Principles
- Prefer systems that can be explained without hand-waving.
- Keep automation boring enough to trust.
- Use abstractions only after the underlying shape is clear.
- Treat performance, operability, and readability as part of the same job.
Elsewhere
The public footprint here is intentionally small. If you want the concise professional version, LinkedIn is the cleanest place to start. GitHub has the code-facing side.