Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Thank you for continuing to share these thorough articles with us.

In my work, I find that communication is the second most-important aspect in any software team.   The first, is seniority.   Don’t give me someone who has only been writing computer programs, in any language at all, for less than ten years, please.   (This pretty-much excludes all L-1 and H-1B Visa holders ... which lack both age and season.)   Give me someone who knows how to understand a technical requirement and to turn that requirement into a set of necessary code-changes, in her head.   Someone who knows how to study an existing piece of production software and to create, not only a change to it, but an effective and thorough test for that change.   Someone who is routinely talking to and among his colleagues, working with them, sharing her thoughts and actively soliciting the thoughts of others.

Post-It™ Notes don’t work, because they are small and lose their stickiness.   What you need is a permanent work-record:   something that tracks the original request and all discussions pertaining to it, as well as the git/SVN/CVS thread of changes made, and a record of all test runs.   Apple has such a system, which they call “Radar,” and as you walk in certain hallways you’ll see big posters which say, “Put It On The Radar.”

To my experience, it is most important that everyone is able to know everything that everyone-else knows, including senior management, about every work-in-progress item, every proposed change, every scheduled change, everything.   A really good tracking system can (greatly help...) do that.   Sticky yellow notes cannot.   Yes, it is fine to sit down each morning with the first cups of coffee, herbal tea, or what-have-you ... ;-) ... but the vital communication is taking place all day.

In reply to Re: Nobody Expects the Agile Imposition (Part VIII): Software Craftsmanship by sundialsvc4
in thread Nobody Expects the Agile Imposition (Part VIII): Software Craftsmanship by eyepopslikeamosquito

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?

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

    How do I use this? | Other CB clients
    Other Users?
    Others browsing the Monastery: (4)
    As of 2019-04-26 09:39 GMT
    Find Nodes?
      Voting Booth?
      I am most likely to install a new module from CPAN if:

      Results (128 votes). Check out past polls.

      • (Sep 10, 2018 at 22:53 UTC) Welcome new users!