|Sent on:||Sunday, January 20, 2013 4:57 PM|
Good point! I tend to think of learning as fun, and implicitly clump them together.On Sun, Jan 20, 2013 at 2:14 PM, Gloria W <[address removed]> wrote:
If you can think of reasons for writing code for free other than philanthropy, equity or learning, I'd love to hear it, and how it worked out for you.On 01/20/[masked]:05 PM, Andrew Beyer wrote:
On Sun, Jan 20, 2013 at 9:18 AM, Gloria W <[address removed]> wrote:
Developers should not do free work unless...
I think it better to simply say that one shouldn't do work with the expectation of some compensation without a specific prior agreement as to the what, when, and how much. There are plenty of reasonable situations where one might _not_ expect compensation,
How about fun? Or solving a problem you face? (ESR's "scratching an itch") Or simply because you can't remember a time you didn't code and aren't sure what you would do with yourself if you stopped? :)
Hopefully there would also be some measure of pay, philanthropy, and learning involved too. And copyright law tends to give you equity in your own creations by default, unless you choose to give it up by agreement. But at least for me, sometimes those are just nice extras, not reasons.
Those are just mine...I'm sure others would come up with reasons of their own. And ultimately isn't it just easier to say "don't do X" rather than come up with an exhaustive list of "only do X,Y,Z..."?