Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Re: Strategies for maintenance of horrible code?

by Moron (Curate)
on Jul 12, 2006 at 12:13 UTC ( #560673=note: print w/replies, xml ) Need Help??

in reply to Strategies for maintenance of horrible code?

Some basic CYA I can see:

1) Ensure there is sufficient functional and technical design documentation against which the routines can be tested.

2) (updated) Make sure there is a sufficiently detailed project plan to include tasks for: systems analysis, functional and technical design, test planning, test script writing (e.g. using Expect), developing, unit-, integrated and functional testing, rework and implementation, to include a GANTT chart of the work done so far and by who to what % of completion, to avoid getting the blame for not meeting poorly conceived targets over which you had no control.

In response to formal testing against the plan, I find it a useful aid to bug-fixing to monitor execution with perl -d, setting breakpoints and examining variables to hunt down which line of code causes each failure.


Free your mind

  • Comment on Re: Strategies for maintenance of horrible code?

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://560673]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (3)
As of 2016-10-23 23:55 GMT
Find Nodes?
    Voting Booth?
    How many different varieties (color, size, etc) of socks do you have in your sock drawer?

    Results (302 votes). Check out past polls.