Every IT manager worth his salt will know that there comes a time when you need to find out more about your underlying libraries/systems than the API documentation tells you. With closed-source systems this often means scouring the web for anecdotal evidence or begging the vendor for more detailed information. Having the source available is the ultimate documentation and can save you lots of hours of guessing and testing. To then have the possibility to change the underlying system to better suit your needs, legally distribute your changes and even maybe merge your changes back into the mainline distribution, can be invaluable. So yes, I think it's a strong selling point. For clueful people, that is.
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||