++ vladb

I thoroughly enjoy and use nodes containing programming style, architecture and other like data and also look for it. I usually only find small bits as side comments in various posts.

I've considered starting a series of nodes to solicit data from talented monks on issues like this, but the OT-ness discussions pretty much derailed my urge :) I'll get over the 'derailed' concept, but it's excellent that you brought it up!

I had titles in mind such as:

It's really more of a list than that. I obviously am aware of the excellent collection of nodes on the CGI issues, but it seemed to me to get it all in one thread or node would be a really excellent resource. Very often what looks like a reasonable way to do something doesn't even closely compare to the answers given by real-world-experienced folks here on PM. And seeing samples in Perl is much preferred in my case. Studying algorithms in texts using languages I'm unfamiliar with isn't always helpful.

I guess I'm in a mode for "what are some commonly accepted best practices for ____?"

In reply to Re: Phantom Menace: Driving forces behind sloppy code/architecture. by tjh
in thread Phantom Menace: Driving forces behind sloppy code/architecture. by vladb

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, details, 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, summary, 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.