, 3 tweets, 2 min read Read on Twitter
"In general the faster you can react the less up front testing you need." Yep.

Almost every org I can think of could stand to reallocate 20% of their eng cycles away from pre-prod testing towards faster, safer deploys (or post-prod validation).
(The one possible exception that springs to mind is @IntercomEng. Last I heard, it took something like 25 sec to run all tests, package and deploy their 🍒RUBY APP🍒)

You only get that after years of dedicated attention, ofc... & pointing @honeycombio at your build pipeline 😉
You cannot prevent failure. Things are failing ✨right now✨ and you have no clue.

Expect it, budget for it, build your system to tolerate lots of it. Fail fast and fix faster. That's where most of you should be spending your scarce engineering cycles.
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Charity Majors
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!