codeinabox@programming.dev to Programming@programming.devEnglish · 4 months agoBias Toward Actionaddyosmani.comexternal-linkmessage-square1fedilinkarrow-up14arrow-down10
arrow-up14arrow-down1external-linkBias Toward Actionaddyosmani.comcodeinabox@programming.dev to Programming@programming.devEnglish · 4 months agomessage-square1fedilink
minus-squarecodeinabox@programming.devOPlinkfedilinkEnglisharrow-up0·4 months agoThere are some really good tips on delivery and best practice, in summary: Speed comes from making the safe thing easy, not from being brave about doing dangerous things. Fast teams have: Feature flags so they can turn things off instantly Monitoring that actually tells them when something’s wrong Rollback procedures they’ve practiced Small changes that are easy to understand when they break Slow teams are stuck because every deploy feels risky. And it is risky, because they don’t have the safety nets.
There are some really good tips on delivery and best practice, in summary: