Personally, I tend to write down everything I want the script to be able to do. Then I write down everything that my boss will expect it to do. Then I wrap my boss's book up in the single sheet of my expectations and pound myself unconscious. When I wake up I usually have a reasonable idea of what I'm going to start with...

OK, actually, I flowchart tasks and APIs first. Much like OOP, I try and figure out what will be done in a general overview and how the big pieces will fit together. Once I have that idea, I pick a small chunk near the middle of the whole shebang and try and get it to respond to my first API spec. Then I flesh it out and start on a neighbor that calls or uses that chunk. At about the 50% level, I start deciding what to re-write. =) There is no such thing as 100% (at least so far)

--
$you = new YOU;
honk() if $you->love(perl)

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.