Re:I Broke Justin.tv
by abstractbill on Tuesday July 19, 2011 @02:12PM
(#2782275)
sorry Bill, they're really quite helpful in the right circumstance
I don't think I've ever claimed they're never useful ;) But I do still believe that, out of the things you listed, they have the lowest utility for the amount of effort involved.
Personally, I would do fully-automated deploy and rollback first, closely followed by monitoring, then code reviews, and then if problems were still slipping through the net I'd tell people to start writing unit tests.
Re:I Broke Justin.tv
by aaronblohowiak on Tuesday July 19, 2011 @04:19PM
(#2782882)
Code review has larger organizational benefits like reducing the "bus factor."
Here are some things we now do at Justin.tv because of experiences like the one you mentioned:
- Everything gets code reviewed
- We have started to introduce tests (sorry Bill, they're really quite helpful in the right circumstance)
- We have extensive monitoring for all systems in case something DOES slip through
- We have fully automated deployment (and rollback)
There's a cost to all of these things, either in setup time or in constant maintenance. When you have few users, maybe they're not worth it - as you grow they become essential.