Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

Re: clean up/professionalism

by markjugg (Curate)
on Feb 13, 2001 at 08:42 UTC ( #58082=note: print w/replies, xml ) Need Help??

in reply to clean up/professionalism

I think the big picture for professionalism in coding goes something like this:
  • Clear and Consistent Code Design
  • Documented
  • Secure
Before I launch a perl project for a client, I add a standard header to all the files, that includes it's name, a short description, a version, and basic info on the license, contact info, and an abbreviated ChangeLog of major changes to the script.

As for "good style", that's a sort of elusive and fuzzy thing. I enjoyed reading the The Practice of Programming which relates to that topic.

As for security, I'm sure you can find a webpage on secure perl programming to measure your work against.

Also, there's nothing like good old peer review to improve code. Perhaps there's a co-worker who would be willing to look things over?


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://58082]
and a soft breeze sighs...

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (5)
As of 2018-07-15 23:19 GMT
Find Nodes?
    Voting Booth?
    It has been suggested to rename Perl 6 in order to boost its marketing potential. Which name would you prefer?

    Results (327 votes). Check out past polls.