Hi Monks,
Not having any formal programming background my usual design process usually goes something like this
* Idea/Requirement
* Start hacking out code
* On-the-fly refactoring of previous hacking
* Some more hacking to get out of the corner I have hacked myself into!
Obviously there is a better way. My question is....is there a better way that suits Perl? I don't want to go into a full formal design process but need some kind of framework within which to sketchout my design and mentally test the feasibilty before I start the coding.It seems as I get more experienced with Perl I see more and more applications and the 'scripts' become larger and larger and more difficult to code in a 'stream of conciousness' style. I have tried listing the 'steps' that the application must perform and fleshing them out with a little detail but it seems to be inadequate once I actually get started coding.
I would appreciate the wisdom of the Monks in my quest to improve my Perl skills.
TeraMarv.