I'm a hacker in the boring, useful sense: I take a problem nobody wants to touch and come back with something that runs. Wedding platforms, link shorteners with an attitude, access control for buildings — same instinct, different Tuesday.
The thing three people already gave up on. I like those. Usually the bug is two layers below where everyone was looking.
Security research habits applied to my own work first. If I can get in through the side door, so can someone less polite.
Front end, back end, the database nobody wants to own, the deploy, the boring emails it sends at 4am. End to end or it isn't done.
Computer engineering by training. Door controllers, smartcards, software radios, boards that only speak in undocumented bytes — we get along fine.
Every wedding site wants one feature the vendor doesn't have, so I built the one that has all of them: per-guest invitation links, code recovery, custom everything. Yes, I'm also using it for my own wedding. Dogfooding, romantically.
Long-term rental management for real buildings with real tenants: leases and maintenance on one side, contractor coordination on the other, and door access that has to work at 2am in February. Software plus the hardware it talks to.
A shortener with a penguin and a mouth on it. Links expire after seven days of neglect, which is more accountability than most infrastructure I've inherited. Built because the domain was too good to leave alone.
A recursive-length-prefix serializer in C with no malloc anywhere. Runs on things that don't have a heap to spare.
Custom builds, Havoc files, and TempestSDR — pulling a monitor's picture out of the air, purely to prove it's possible.
Javacard applets that hold keys and sign transactions, plus homemade AirTags on Apple's Find My network. Both more fun than they sound.
I'm not looking for a job. I'm looking for interesting problems — mine, yours, ideally weird ones.