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.
-
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.
|
