Re: Tips for managing Perl projects?

There's far too many good comments for me to add too much, but I'll try two anyway:

In the U.S. and large enough? Think Sarbanes-Oxley compliance...
Operationally, anything you do to touch access and account creation may be subject to SOX compliance. We're in the midst of it now. At them moment, they don't much care about how the code looks, but they do care about who can run utilities and where the output lives. Does it touch your financials or order-to-cash? Then, it's definitely a consideration.
Print out gold versions for offsite storage...
Sure, you're making digital copies for DR (right? ... the only right answer is yes). Print paper of major revisions, put a copy in the fire safe and take a copy home (assuming that's not a license violation... if it is, send a copy home with a company officer).

I know these sound pretty dorky in comparison to the great "best practices" coding comments above. But, this frequently gets overlooked in project management. It's even worse when it's a critical admin utility. Make sure the code is auditable. Make sure there's a copy offsite.

Amatuers discuss tactics. Professionals discuss logistics. And... my cat's breath smells like cat food.

Comment on Re: Tips for managing Perl projects?

Replies are listed 'Best First'.

Re^2: Tips for managing Perl projects?
by radiantmatrix (Parson) on Dec 17, 2004 at 15:18 UTC

> Sure, you're making digital copies for DR (right? ... the only right answer is yes). Print paper of major revisions, put a copy in the fire safe and take a copy home (assuming that's not a license violation... if it is, send a copy home with a company officer).

For code preservation and data recovery, I have these rules:

Developers each have a "local" RC repository on their primary network resource (that is, home drive on Windows, /home/$USER/net on our Linux systems). All WIP is checked into that repository for every change. (Changes are demarked when the dev runs a test).
All changes are checked into site-daily RC at EoD.
Any change must be eventually checked into the site-dev RC, but must pass all unit-tests first. Unit tests are run automatically on checked-in code.
All repositories are backed up daily. (The normal corp. process takes care of having off-site copies and rotations)
Daily/Weekly RC snapshots are backed up to DVD-RW, and encrypted to the VP and project manager's keys. One copy goes home with the VP weekly, and one goes home with the project manager daily.

radiantmatrix
require General::Disclaimer; s//2fde04abe76c036c9074586c1/; while(m/(.)/g){print substr(' ,JPacehklnorstu',hex($1),1)}

[reply]


Pathologically Eclectic Rubbish Lister
	PerlMonks