
Code Is a Liability

#168 - Serverless as a Game Changer - Joseph Emison
Topic 6 of 14
Published Mar 25, 2024 · Clip 27:54–32:30 (4:37)
Joe explains code is a liability because it must be maintained, tested, and kept working; the asset is the experience built. He describes Branch's waterfall process: first ask whether anything needs to be built at all (buy SaaS), then down scope requests to tiny increments with a promise of continuous iteration, training the organization to think small. He also distinguishes declarative YAML/CloudFormation (low maintenance, like a yarn.lock file) from Pulumi/CDK code, which gets edited frequently and should be minimized.