Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
It's not so much that there is an enemy, but that we can deal with life in the same way in different situations. Different environments emphasize different facets of a solution and add perspective.

I can't carry any metaphor too far because ultimately one thing is not the other, so they are different. The trick is to find the areas where one can beneffit from knowledge of the other without experiencing it.

--
brian d foy <bdfoy@cpan.org>

In reply to Re^2: Programming is combat by brian_d_foy
in thread Programming is combat by brian_d_foy

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



  • 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! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    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
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    [marinersk]: sub newtest{my $expected_result = &target('foo'); my $actual_result = &target('foo'); if ($actual_result eq $expected_result) { &tdd_success(); } else { &tdd_fail(); } } # Test works after three years!
    [choroba]: or nobody bothered...
    [choroba]: The problem was bigger, as the test tried to call a method that didn't exist anymore
    [marinersk]: :: ducking ::
    [choroba]: because, someone renamed the method, but didn't notice it was used in the test, as the test was skipped
    [marinersk]: Well, if the method doesn't exist, it would be hard to pass the test.
    [choroba]: later, someone removed the new method, as all its usage places were safe, but didn't notice the test still used the old name
    [choroba]: fortunately, it wasn't that hard to replace the method and fix a few remaining failures due to the changes we did to the codebase over the years
    [marinersk]: choroba Sounds like a process improvement opportunity; tests may not all need to be run, but they should all be compiled with perl -c before check-in/promotion happens.
    [choroba]: so, now I have the test, so I can start making changes in the code. Back to the original ticket, yay!

    How do I use this? | Other CB clients
    Other Users?
    Others pondering the Monastery: (14)
    As of 2017-05-25 15:10 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?