I have tried several approaches to the baby-perl versus no-holds-barred-perl problem. I think the best approach is to write code that is an achievable challenge for your audience to understand. It should be difficult enough that the reader feels a sense of accomplishment in reading it. It should not be so difficult that the reader does not stand a chance.

More difficult code can be buried within a module. A module is an extension of the language itself. If properly written, it can be used without having to understand how it works. The audience is simply told, "Use this module and don't worry."

Japhy writes a clear explanation sufficient to guide a novice through the advanced code in the example. His explanation proves to us why we should all buy Japhy's book, should he decide to write it! Not all of us have the time or talent to write such a clear explanation. We should tame our code until it is barely within the reach of our audience. Japhy tames his code by showing how it is developed.

I have the pleasure of working with a fellow who doesn't know perl at all, but he is confident that he will be able to follow, use, and modify my code. He has been reading my copy of Learning Perl. His willingness to stretch his capabilities makes him more valuable and more fun to work with. He knows he can ask me questions if he runs into something opaque. He doesn't want to suppress my creativity with his temporary personal limitations. Between his confidence and my somewhat conservative coding style, we enjoy the collaboration.

It should work perfectly the first time! - toma

---

---

• 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 How to display code and escape characters are good places to start.