News for hackers. Stuff that matters.
Re:Monitoring Sucks. But Monitoring as Testing Sucks A Lot More by Spooky23 on Thursday July 19, 2012 @12:46PM (#4266863)
I think the root of what this guy is ranting about is that many web people seem to confuse rapid release iteration with rapid engineering iteration. The folks who do this don't understand that the frameworks that they are using are taking care of their lack of forethought -- but will only do so for a limited time.

Design, implementation and testing are different disciplines that are essential to reliable systems. You may not need to formally embrace all of them at a given point in time (or product cycle), but claiming that "testing" is a fraud or that "roll back" is mythical is just a demonstration that the speaker doesn't have a mature engineering background.

Re:Monitoring Sucks. But Monitoring as Testing Sucks A Lot More by NoahSussman on Sunday July 22, 2012 @09:19PM (#4279112)
I'm pretty sure that I didn't say that testing is a fraud. Although I did say that I think production monitoring should be set up on day one of a new project, while unit testing can wait until the project has matured a bit. I also said that unit testing isn't going to be nearly as helpful without having production monitoring in place. And I said that with production monitoring in place it's possible to get by with a lot less unit testing than has been historically prescribed -- which is a good thing since production monitoring systems tend to be less expensive to maintain than unit tests.

I did at one point say "there's no such thing as rolling back." This is an idea to which I'm pretty dedicated. I've seen first hand many times that using an SCM revert command to attempt to restore "last good state" is a risky endeavor, especially when a large changeset is involved.