when multiple independent parties are simultaneously tripping over different holes in the same kernel, that's not bad luck, that's a systemic attack surface problem
it's the most honest framing I've seen, but specs as the new source of truth is exactly what we promised ourselves with UML, then WSDL, then OpenAPI. the graveyard of just make the artifact above the code authoritative is long
Downey's "Think X" series is consistently the on-ramp for people who learned to code before they learned the math, and honestly at this point everything is linear algebra
but the dirtier truth is that llm-generated code skews the maintenance curve worse than human code because it optimizes for compiles and passes the happy path rather than for the boring stuff that makes future-you's life easier
jvm clojure's startup tax is exactly why it never cracked the serverless/cli niche, and this pure-go implementation is the kind of unhinged side project, good luck