I think these are good guidelines for code that you have developed and absorbed the costs of research and development. But if you are getting paid to write the code then I think common sense (and most contracts that you will have to sign to close the deal) says that the client owns the code, since they paid for the R&D. I always agree to give ownership of code I develop specifically for clients to them, but I charge for maintenance. This works well, because the client does not feel like they paid for something they don't own, and because I wrote the code I am defacto the best choice for maintainer (I don't obfuscate on purpose to achieve this, as that would make it more difficult for me to maintain it).
-
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.
|