From puzzles to products
summary
Argues that programming is mostly about changing systems not just writing code, so priorities shift to designing change over purity of internal architecture. Emphasizes concrete techniques: feature flags and phased rollouts, backwards compatibility and data migrations, and adding observability hooks to measure who still uses old behavior. Shows code patterns that explicitly carry history, explains how to coordinate external teams and product workflows to make upgrades safe and measurable.
AI-written summary · about
related talks
40mThe Best Programmer I Know
43mThursday Keynote -- What Programming is Really About
35mCraft, Engineering, and the Essence of Programming
34mHow do our ideas about coding affect the software we create?
52mFrom Code to Complexity: Shifting to Systems Thinking in Software Development
01h 02mAround Learning
27m'The Art of Software Development'
01h 00mThe Influential Software Engineer