Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on The Configuration Complexity Clock (2012). Parent comment
> But actually a config change is just as dangerous as a code change, and the same level of testing is usually appropriate
Points well made, unarguably so
> In my experience many - perhaps most - production outages tend to be caused by "config changes".
I have no comparable experience but it sounds all too plausible and I shall bear that strongly in mind henceforth.
> "Config" tends to not be treated the same way [as code] [...]
From there to the end is brilliant. Thanks so much for such an excellent response. I'm going to print this out and keep it.
There are no comments on this comment yet.
> But actually a config change is just as dangerous as a code change, and the same level of testing is usually appropriate
Points well made, unarguably so
> In my experience many - perhaps most - production outages tend to be caused by "config changes".
I have no comparable experience but it sounds all too plausible and I shall bear that strongly in mind henceforth.
> "Config" tends to not be treated the same way [as code] [...]
From there to the end is brilliant. Thanks so much for such an excellent response. I'm going to print this out and keep it.