Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

Re^2: Developing code to be a module

by Utilitarian (Vicar)
on May 01, 2013 at 10:02 UTC ( #1031540=note: print w/replies, xml ) Need Help??

in reply to Re: Developing code to be a module
in thread Developing code to be a module

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.

print "Good ",qw(night morning afternoon evening)[(localtime)[2]/6]," fellow monks."

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1031540]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (7)
As of 2017-12-11 20:24 GMT
Find Nodes?
    Voting Booth?
    What programming language do you hate the most?

    Results (311 votes). Check out past polls.