Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Screw understanding Perl. Write something about understanding programming. This mythical book would start with logic, work through metalogic, wend its way through data structures, have some tea and biscuits with people skills, discuss verification of design and function, and, on page 726, introduce the concept of the editor. At no time does this book have a single code listing in any language. Period. Oh, and it'd be accessible to my very smart 10-year old, yet engaging enough for a college student.

Why, you may ask? Because people can write garbage in every language. And, frankly, 99.9999999% of all programs are GARBAGE, pure and simple. They are unrecoverable, barely maintainable, buggy and insecure dreck.

"Oh, dragonchild. You're exagerrating." Uh ... no, I'm not. And every single person who reads this that has worked in more than 3 companies is unconciously nodding their collective heads right now. If enough people read this at the same time, there'd be a measurable wobble in the Earth's orbit. It is really and truly that bad.


My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re: What's missing in Perl books? by dragonchild
in thread What's missing in Perl books? 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":



  • 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.
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?Last hourOther CB clients
Other Users?
Others surveying the Monastery: (3)
As of 2024-03-29 02:22 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found