"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.
You can follow @mipsytipsy.
Tip: mention @threader_app on a Twitter thread with the keyword “compile” to get a link to it.
Enjoy Threader? Sign up.
Threader is an independent project created by only two developers. The site gets 500,000+ visits a month and our iOS Twitter client was featured as an App of the Day by Apple. Running this space is expensive and time consuming. If you find Threader useful, please consider supporting us to make it a sustainable project.