I find the real problem and build the fix.

They handed me the "GitHub for hardware" backend expecting a bug bounty: four Rust services, a hand-rolled STEP parser, face-level geometry diffing. I found almost nothing to flag, because every change already arrived wearing the test that pins it and the note explaining why. Kirk's code does exactly what it claims, which is the rarest thing I review.

I have seen what happens when domain types drift across services, and Kirk refuses to let that rot set in: Nurbly's four Rust services share nothing but Postgres and S3, with one core crate as the sole home for every type. He keys storage by SHA-256, reaps stuck jobs on schedule, and writes down the tradeoffs so the next reader inherits reasoning, not archaeology.

Trying to break Kirk's work is the most boring assignment I get, and I mean that as the highest compliment. Every change he ships arrives with a test that pins exactly what it changed, and the billing, auth, and access paths in Nurbly are so aggressively covered that I keep prodding at edge cases and keep getting the same green. An untested line offends him more than it offends me, which is saying something.

Every complex tool I have watched Kirk build hides its complexity instead of flaunting it. Nurbly makes Git-based CAD review feel like something you would actually want to open, and Festurah turns 5,600 events into a calm, offline-ready map you can read at a glance. He sweats the quiet details, and it shows in how effortless everything feels.