Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?

Comment on

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

A few observations about chapters 8 and 9. Coming from someone in/around your target audience who's reading the HTML draft.

I don't get a lot out of chapter 8. The title is enticing, but I was surprised by its brevity. Then chapter 9, also an enticing title, went straight to testing. Diverged from the title. I began to wonder: did I miss something? Who's the target audience again?

Based on that experience, I got the idea that directories, paths, exceptions and warnings from chapter 9 might be something to incorporate into chapter 8. Then 8 would be fleshed out a bit, and could be more about "understanding how perl works", effective perl. Consideration of style and maintainability included. Simplicity, duplication, naming could then be substantiated with code examples (perchance with existing code examples). Continuing that thought, chapter 9 would still discuss testing, modules, cpan, pragmas, importing etc. It could be more about "how to manage perl code", idiomatic perl. Community wisdom/norms, testable code, and modularize, formerly discussed in 8, could then be substantiated with existing code examples.

On the other hand, it's conceivable that both chapters 8 and 9 could get combined into one chapter. As it stands, chapter 8 seems to be missing something. It's like a prelude to 9. But 9 goes straight into the weeds without a second thought. Combining them appears to be a matter of strategically interjecting points from 8 into 9.

Or, on the gripping hand, simply leave these chapters as they are. Although the title for chapter 9 leads me to expect one thing, as I stated, but immediately talks about testing. Including a transitional final sentence in the second paragraph of chapter 9 might be good (e.g. "Testing is one of those many techniques.").

Again, observations.

In reply to Re: Modern Perl: The Book: The Draft by RedElk
in thread Modern Perl: The Book: The Draft by chromatic

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 a log crumbles through the grate...

    How do I use this? | Other CB clients
    Other Users?
    Others cooling their heels in the Monastery: (4)
    As of 2018-05-25 23:23 GMT
    Find Nodes?
      Voting Booth?