Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
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:

  1. You get pretty much 100% test coverage for free.
  2. You always know when you have got a piece of code working.
  3. You always know if a new piece of code breaks something.
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.


In reply to Re: My number 1 tip for developers. by adrianh
in thread My number 1 tip for developers. by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <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>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (4)
As of 2022-05-21 13:45 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Do you prefer to work remotely?



    Results (76 votes). Check out past polls.

    Notices?