Reliability, Innovation, Time to Market: Choose All Three
summary
Claims that reliability, innovation and speed are simultaneously achievable by making reliability a hard requirement and running parallel certification invariant alongside development. Example: two teams build the same avionics product; one finishes features fast but ends up >2 years late in certification, the other integrates certification and ships only a few months late. Engineering stack uses state-space randomized walk, deterministic replay via chain-hash deterministic replay, Folly/co-routines, single-process simulations with seeded parallel runs and targeted state partitioning to find and fix dozens-link failure chains.
AI-written summary · about
chapters (5)
related talks
52mBeyond Features
27mThe Perverse Incentives of Reliability
34mReliability and Engineering Requirements
29mEconomies of Speed
22mOptimizing Product Development: Balancing Speed, Quality, and Process
28mPick any Three: Good, Fast, and Safe. DevOps from Scratch
37mSlow and boring: Secrets to building reliable software
45mThe Goldilocks Problem of Software Delivery
