field-notes/
24 items
| Name | Description |
|---|---|
| E1.md | Dedicated engineer for a 3,500-server global game |
| E2.md | Stopping 3 a.m. DDoS attacks with no one on the keyboard |
| E3.md | Deploying to 500 servers, 80% faster |
| E4.md | Infrastructure status at a glance, in real time |
| E5.md | From a monthly security review to a daily automatic one |
| E6.md | Making sure the same finding never comes back |
| E7.md | One codebase instead of copied infrastructure code |
| E8.md | Moving a live game between clouds without stopping it |
| E9.md | Redesigning a tangle of firewall rules |
| E10.md | Stopping attacks on game servers |
| E11.md | Knowing first when something goes wrong |
| E12.md | An AI that writes infrastructure code from a plain request |
| E13.md | Setting a security baseline for a financial cloud that had none |
| E14.md | Only the access you need, recorded in code |
| E15.md | Alerts from many accounts on one screen |
| E16.md | "Turned on" and "actually blocking" are different things |
| E17.md | Operations tools that run on a PC with no internet |
| E18.md | Explaining in the language the other person already knows |
| E19.md | Less time spent capturing packets |
| E20.md | Owning the security checks that repeat every month |
| E21.md | A security review that tested requirements with numbers |
| P1.md | A virtual company staffed by 11 AI employees |
| P2.md | A service that answers "can these two talk?" in two clicks |
| P3.md | A public repository series for this portfolio |