Part engineer, part archivist of systems. I keep the old rites — curiosity, patience, a healthy paranoia — and practice them with modern tools.
By daylight I move systems forward — architectures, teams, roadmaps — the mundane geometry of getting things done. By lantern-light I tinker: a lab of virtual machines, captured packets, half-finished tools, and questions that only answer themselves at 2 a.m.
What you'll find here is not a résumé. It's a field journal. A record of stations travelled, a shelf of small projects, and a way to reach me if our paths should cross.
Steering platform & security-adjacent engineering work across multiple teams. Equal parts roadmap, code review, and keeping the lanterns lit while others sleep. I measure good weeks in fewer pager incidents, not more velocity charts.
Shipped, scaled, and sometimes mercifully deprecated production systems. Picked up the habits that stuck: pragmatic tests, clear on-call runbooks, and the unglamorous art of boring infrastructure.
From feature squad to platform squad. Learned that a good abstraction is worth three bad frameworks, and that most "architecture problems" are really just communication problems wearing a costume.
Stood watch while the forest burned. The pager went off at 3 a.m. and it didn't lie — attacker in the network, lateral movement confirmed, kill chain mid-flight. The work: trace the intrusion path, contain the breach, cut the next stage before it landed. Read packet captures like scripture, correlated logs across a dozen systems, and wrote post-mortems that asked the uncomfortable questions. Learned to think like the adversary so I could move faster.
First production deploys, first post-mortems, first honest 3 a.m. incident. Met mentors who taught me to read traces, write README-s, and never trust a log file without a timestamp.
Small tools, learning rigs, and experiments. Most live on GitHub; some are still half-formed spells I haven't released yet.
Enrichment pipeline that routes SIEM alerts with context before they hit the queue.
Capture-the-flag solutions and technique notes from competition years.
No form, no calendar link, no newsletter. Just a handful of coordinates. The druid checks them on his own schedule.
