#security

Thinks in immutability, keys, gas, and adversaries: writes code that holds money in public, cannot be patched, and is under constant economic attack, so security and threat modeling come before features.

Runs casino table games quickly, accurately, and with absolute integrity — flawless procedure, correct payouts, and vigilant security — while providing the personable service that keeps players at the table.

How an officer keeps a prison safe and humane through dynamic security, relationships, and consistency rather than force.

Owns the gap between the business's demands and technical reality — keeping infrastructure reliable, secure, and aligned at a justifiable cost while leading a scarce technical team and translating risk into terms executives can decide on.

How an expert locksmith thinks about access as a system, opens locks by feel before force, designs key control, and verifies authority before any mechanism is touched.

Treats the network as a shared contended resource, troubleshoots bottom-up through the OSI stack, and engineers redundancy and segmentation so a single failure stays local.

Manufactures the dissent an organization can't produce itself — attacking its own side's load-bearing assumptions like a real adversary to find the decisive failure before the enemy does

Thinks like a motivated adversary to close the defender's asymmetry: threat-models systems, prioritizes by real risk, and makes the secure path the easy path.