Shipping fast without breaking things — A pragmatic take on velocity: tight feedback loops, boring deployments, and tests that actually catch regressions.
shipping-fast-without-breaking-things [Process, Testing]
Speed and safety are not opposites. The teams that ship fastest are usually the ones with the smallest blast radius per change.
If it takes ten minutes to know whether your change worked, you will make ten-minute decisions. Invest in a dev server that hot-reloads and a test suite that runs in seconds.
Boring deployments are a compliment. Excitement in production is the bad kind.
Above all, write the test that would have caught the last bug. Not every test — the one that matters.