Re:Putting out fires at 37signals: The on-call programmer
by Smudge on Monday April 16, 2012 @07:02PM
(#3849959)
But root-cause analysis of the issues that arise is still important, right? Tracing customer-impacting issues back to the decisions that might have caused them? Perhaps not even particular bugs or parts of the product, but architectural decisions as a whole? Or even organizational processes? You can throw money at live support until the end of time, but the only way to reduce that cost is by addressing problems at the source, be it code or process, or something else... (right?)
[ Parent
| on HN ]
Re:Putting out fires at 37signals: The on-call programmer
by vitovito on Monday April 16, 2012 @07:25PM
(#3850055)
Sure, and the "live" team is made up of people from the regular "new feature" team, rotated in and out so they all understand the impact their code has.
But, in a product that gets used by lots of real users, shit happens. You're never going to get everything right the first time.