If I start without planning, I'm like a car without a steering wheel. But almost always the actual writing reveals things that just aren't right with the plan - missing data or misunderstood documentation, for example. So I take a step back and reassess what data/algorithms/architecture is needed.
I personally would recommend that you start your coding projects - whether they be script or module - with something that you can code a bit and run, code a bit and run. That way you get a reality check on your plan and your plan gets to continually take new facts and understandings into account.
Best, beth
In reply to Re: what are all the things to be considered to write a effective perl script or module?
by ELISHEVA
in thread what are all the things to be considered to write a effective perl script or module?
by balakrishnan
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |