Reducing the fear of go-live
summary
Concrete practices for calmer deploys: keep reliable unit tests, regular code reviews and deploy rehearsals, measure rollback time and error rate, and prefer small releases and canary rollouts so problems affect few users. Advice includes specific readiness signals (stable metrics over N days, automated recovery under X minutes) and cultural moves to increase trust in the team like shared ownership, pairing, and blameless postmortems. Real projects that were rushed and ones confidently released are compared.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:37If you think you understand quantum mechanics, you don't understand quantum mechanics
- 13:38Shor's Algorithm Prime Factorization Bitcoin changes (not for NP-hard?s)
- 18:27There are other PQC options... - longer keys (1000-x longer RSA) - Multivar quadratic equations - Hashes McEliece / Goppa codes
- 18:58It's efficient, looks effective against quantum Bonus: homomorphic encryption Lattices - ?- Ring Learning with Errors For symmetric and asymmetric encryption
- 19:43Server and client agree on a cipher that both understand AES-256 toughest Current key exchange step is unsafe too
- 21:41by Mirek Kratochvil McEliece Crypto System for Encryption, hash for Signing As a result - needs two sets of public/private keys Modeled after GPG commands, but has different output
- 24:46When will quantum computers exist? Do brains use quantum computation? Will new crypto survive testing?
related talks
26mThe emotional chaos of deploying code
41mContinuous delivery in 10 easy mistakes
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
33m7 habits of a high performing team
37mFear Driven Development
38mJust Ship It!
33mSoftware development practices for companies that want to make an impact
30m10 Ways to Improve How You Ship Software