I don't think you're being negative. I personally do not like the idea that things that can be created cannot be owned. This line of thinking punishes creators and justifies thieves. (Not to say that IP issues are solved in the world or work perfectly.) I think the teacher analogy is false as teaching is, in itself, not a creative act. A sidebar to that: I was a contracted teacher who created a large amount of custom curricula and materials to make my own work much easier. Since this was not a formal part of my job it was considered mine and the school paid me quite a bit of money to keep it, and clean it up a bit for new teachers to use, when my contract ended.
I do think you've hit upon an issue of architect versus craftsman. When I use Moose, as someone else mentioned, I'm not creating as much as crafting. In this trade the lines between architect and craftsman get blurry. I've had patches and bug reports to a couple major kits accepted, and had my code re-used by two Perl luminaries in particular. Does it make me an architect? No-ish...? It's a weird world we live in. I do really like it, though.
(update: fixed a compound word.)
-
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.
|