3 ms·
I discovered a similar problem with writing, which is that writing an email or a comment takes no time at all, but when someone is paying for what I write it ta
by ChuckMcM 11y ago
I discovered a similar problem with writing, which is that writing an email or a comment takes no time at all, but when someone is paying for what I write it takes a lot more effort. I wrote a column for a couple of years and it wasn't until the second year that I actually took my editors advice to just send her the first version and work on it collaboratively rather than try to get it perfect.
I see side projects also get bushwacked by this mental shift.
- teddyh 11y agoStudies Find Reward Often No Motivator http://www.gnu.org/philosophy/motivation.html http://www.gnu.org/philosophy/motivation.html
- ChuckMcM 11y agoThat was a good read, but there was a different mechanism at work for me. When I do something for free, and someone complains about it or finds it wanting, it does not bother me. Sort of like "Double your money back on Free Advice you don't like." But when I am being paid to provide the thing I am providing, a big sense of my wanting to make sure they are getting their value kicks in, and since I undervalue my time tremendously I try to over deliver on value. And that slows me down. Letting my editor have an early draft let her decide if there was sufficient value and on at least one occasion she took my column as written and said, "This is great, we'll have proofs ready tomorrow." Had I not sent the draft I would have spent at least another week writing and re-writing.
- eschutte2 11y agoBoy, can I identify with this. It can be very hard to turn off that impulse to over-deliver. It can also be hard to objectively look at your own limitations and not overcommit yourself, and hard to adjust when you find out too late you've overcommitted.
- kelnos 11y agoI guess I've just become a bit more jaded. Or maybe I always have been. I used to maintain a good amount of open source stuff, and the entitled complaints really got to me. But if I'm being paid for something, I feel the obligation to deliver what I've promised, and I feel bad if I fall short. I do struggle sometimes with valuing my time "correctly", but overall I think I've experienced less stress building software for a paycheck vs. dealing with the (minority of) ungrateful leeches in the open source community.
- fsloth 11y ago"the entitled complaints really got to me." Having done some voluntary work long time ago - I would say providing value to a community in any context seldom pays in direct gratitude. In direct communication, complaints are always more likely than compliments. The value must come from somewhere else than direct feedback from beneficiaries, like observing the thing you just pulled off being enjoyed by a lot of people and being pleased of it. The corollary to this is that it's much more enjoyable to work for free in a friendly group than alone because then the company and support of peers can be an equivalent source of joy. I suppose a lone free software project lacks these both, unless one can visualize the value by looking at the number of downloads...
- hiou 11y agoI find this so interesting as I have always felt if someone is paying me I make sure to give them exactly what they paid for and not a bit more. A market economy does not allow me generosity. When I'm writing code for myself or others the upside feels boundless as appreciation and enjoyment are much more difficult to quantify.
- JoeAltmaier 11y agoI worked differently as a contractor. I over-delivered by a little, especially if it was easy to do. By delivering code on time plus a feature or mockup of the next stage, I often got a follow-on contract. Its like the novels that end with "Here's a chapter from their next book!"
- mdpopescu 11y agoThis reminds me of Heinlein's rule three: You Must Refrain From Rewriting, Except to Editorial Order
- ChuckMcM 11y agoHeh Jerry Pournelle, another science fiction author, used to say "The secret of good writing, is re-writing." :-)