Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Lecar_red (5694)

Lecar_red
  (email not shown publicly)

Journal of Lecar_red (5694)

Thursday March 10, 2005
05:25 PM

Taking an idea and turning it into software

[ #23594 ]
I've been frustrated with not being able to take an idea and turn in it to software. I seem to have trouble breaking it into writable (is that a word?) pieces. I guess you could call them requirements... I seem to get spin in the details. Any ideas out there?
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • If you're getting overwhelmed by all the details, take a piece that you've got a pretty good understanding of an implement that. Something things will then coalese around it. If nothing else it elminates the Tyranny of the Blank Page.

    Otherwise just don't sweat the details. Get some known subset working and start using it, adding features as you need. This approach requires some knowledge of Refactoring.