changing complex code requires extensive testing before trusting it.
It isn't a matter of not imagining this use case - it is going beyond
and imagining if something goes wrong, or if you had to take over as
a replacement sysadmin where someone had made one-off changes like
that and even if they work you won't be able to get any help
understanding or maintaining them.
No one ever said that the changes wouldn't be tested. I'll probably run the new system for weeks, watching the logs carefully and making any necessary changes, before trusting it.
On Fri, 15 Mar 2013, Adam Goryachev wrote: > custom > versions of software always lead to pain (in my experience), so unless
> there is some major commercial advantage, then I steer clear.
Interesting point of view. I don't agree. I always considered the ability to make changes to the
software to make it do what *I* want it to (rather than succumbing to
what the original developer thinks I want it to do) as one of the
hallmarks of opensource software. If you want to use software as-is, that can be beneficial too: http://news.slashdot.org/story/13/03/13/2052226/why-freeloaders-are-essential-to-foss-project-success
V2 of the patch (unified, per request, even though there is no real standard for diff/patch) attached, if anyone cares.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
