What do you do before you start coding?
I have a reasonably complicated coding task ahead of me -- a dash of Oracle DBD, a sprinkle of COM, 2 cups of reading and parsing data, and the usual goodness of Perl. I have done the "assessment" of the situation, looked at the incoming, pondered the in-between, and scoped the outgoing.
What do I do in the "design" phase? Unfortunately, I am allergic to buzzwords, but others in the team seem to be talking UML, state and sequence diagrams, sizing analysis, and data flow, data event, and domain class modeling (and the ilk) (Update: the others in the team are not doing Perl tasks -- they have their own DB or VB specific tasks. I am the only Perl/DB person. They want to use all the mentioned tools and techniques for their portions). I want to do everything that is essential to creating a good Perl program, and leaving it in an easy to understand state for the future. I don't want to do anything extra other than that. The tools available to me are MS-Office, Project, Visio, and various text editors.
WWPMD?
In reply to "Designing" a Perl program by punkish
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |