one thing that sometimes works for me is this:
if you have working on the project 'top-down' switch to 'bottom-up', and vice versa.
I.e. if you have the main loop/sequence written, but some (or all) of the functionality isn't there, think of a bottom level function/class that you think you will need and write that, even if it isn't clear exactly how you'll hook it up. As a bonus, I usually write more generically useful and robust modules when doing it this way.
But if you have just been gathering lots of little things and aren't quite sure how they are going to go together, go ahead and write the main loop. Fill it full of function calls that do absolutely nothing.
Also, and this is really hit of miss, make a check list of things to do for the project to be done. Find the easiest thing on the list, and do it. Then check it off the list. Sometimes the mental reward of 'see I got _something_ done' is enough to kickstart me.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||