Been thinking about this. Conventional wisdom says you need a comprehensive set of regression tests to go green before you release code. /1https://twitter.com/samphippen/status/868918641189949442 …
-
-
Replying to @sarahmei
You want to know that your changes didn't break something elsewhere in the app. But there are ways to tell other than a regression suite. 2/
3 replies 2 retweets 10 likes -
Replying to @sarahmei
Especially with the rise of more sophisticated monitoring and better understanding of error rates (vs uptime) on the operational side. 3/
3 replies 2 retweets 13 likes -
Replying to @sarahmei
With sufficiently advanced monitoring & enough scale, it's a realistic strategy to write code, push it to prod, & watch the error rates. 4/
17 replies 36 retweets 63 likes -
Replying to @sarahmei
If something in another part of the app breaks, it'll be apparent very quickly in your error rates. You can either fix or roll back. 5/
3 replies 3 retweets 10 likes -
Replying to @sarahmei
You're basically letting your monitoring system play the role that a regression suite & continuous integration play on other teams. 6/
6 replies 8 retweets 21 likes -
Replying to @sarahmei
I'd rather have a test suite than a pagerduty rotatoin
2 replies 1 retweet 4 likes
Not that having one means you don't need the other
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.