Display controls that account for the hardware behind them. Built-in and external displays, native control paths, and a way back when something misbehaves.
Inside the buildNative control paths & recovery+
My contribution
Built a Swift/macOS utility with native and DDC/CI control paths, multi-display configuration, offline operation, and reset and recovery controls.
The constraint
Different monitors expose different controls. A consistent interface still needs to account for the device and the control path underneath it.
The engineering decision
Treat reset and recovery as part of the product, not an afterthought. Give the user an explicit route back when a setting or display behaves unexpectedly.
A property is one address. Its records are everywhere.
I brought municipal records into one property-research workflow. The important part isn’t just finding data. It’s showing where it came from, when it was published, and what it can’t tell you.
Built mobile, desktop, web, and civic-data products. Took work through requirements, development, troubleshooting, testing, documentation, and release readiness.