Start1 by typing as much as code as you know will work
In my opinion an even better option is to start by writing a test for what you want to happen, then write the code to make that test pass. Repeat until code done.
Test Driven Development takes a little getting used to, but works very well in my experience. Advantages include:
So code a "caller" that uses that interface. In perl modules I tend to code this as a "main' program within the same file.
You can also do this sort of thing with Test::More and friends - and have the advantage of having something you can move to a test script later on. So instead of:
package main; use strict; my $doit = doit->new(); my @data = 1..10; print $doit->enumerate( \@data );
do something like:
package main; use strict; use Test::More 'no_plan'; isa_ok my $doit = doit->new(), 'doit'; my @data = 1..10; is_deeply [$doit->enumerate( \@data )], [1..10], 'enumerate works';
Then you don't have to think about whether what's being printed out is correct.
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>