|
I almost feel like saying, "If you would do your job for free, quit", just to be flamebait-ey. Hewever, I think there's a level of professionalism that comes with getting paid (ie: you feel bad slacking off reading HN), but if you're working for free, then I can see it turning into: "Hey, let's try framework Z, because it looks like fun!" (not because of client requirements). "OH LOOK, HASKELL ON A HORSE! I've never written Haskell, but let's try it for the Foo subsystem!" Yes, this is too simplistic, ie the open source community. Usually when I work on open source stuff it falls out of client work (I want X to be better, I found a bug in Y, etc). Then again, I've been a contractor for the last 8 years, so I might have a different view than a independent software vendor with their own product lineup. (Yes, I am working on my own product, but not because I want to work for free: it's because I want to create a revenue stream and get paid.) |