I agree that a blog is not a good place to put code (or documentation, for that matter), but calling it a waste of time in general is over-generalized.
A blog is a very good tool for letting others know what you're working on, and if there's a big public interest in the things you do, then it's really worth the time. The alternatives are mailing lists (to which usually most people who would read your blog aren't subscribed), and answering questions directly - which is much more time consuming, and reaches even less people.
The point is of course that you should only blog if you actually have something to say, and which is of interest to at least some part of the Perl community.
I for one love to read more from the testing/qa people, and from the Perl 6 and Parrot folks (naturally, because my main interest is in the same area).
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||