Many of us toiling at the "adminface" will develop a "-e" solution to a specific problem, which subsequently becomes a script as it "got a little complex".

When it becomes a script strictures are applied and the code get slightly neater.

Then a couple of weeks/months/years later you end up automating a process around this script, at which point it needs to be "modularised".

At that point we add tests so that future development doesn't lead to regressions etc... and our humble script has made it through the admin's software lifecycle, it bears a passing resemblance to a developers software lifecycle after this stage has been reached.

Personally I wouldn't count the failure to anticipate a simple flip-flop filter with an END block becoming a full blown log file parsing tool for a production service as bad coding.