[00] Origin Story — Where SASE Came From
SASE started as a coping mechanism. I was a software engineer at Google, working in codebases and on teams large enough that the everyday open-source playbook — read a file, change a file, send a PR — stops being a complete description of the job. The rigor that scales to those environments is not just writing code rigor; it is surrounding the code rigor: durable plans, review state that outlives a chat window, dependencies between changes, retries that don't lose context, and handoffs that someone else can pick up cold.