| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Line: 69 to 69 | ||||||||
| This is related to Demarco and Lister's discussion of "flow" in Peopleware. Here's Joel Spolsky's review of Peopleware: http://www.amazon.com/review/RYVTUPDAUANZW Somewhat related is the question of what really motivates creative people. Turns out it's not money: http://www.youtube.com/watch?v=rrkrvAUbU9Y Well-researched presentation about software management (team size, hours, etc): http://www.lostgarden.com/2008/09/rules-of-productivity-presentation.html | ||||||||
| Added: | ||||||||
| > > | Even very short interruptions have a surprisingly large impact on error rates: http://www.futurity.org/top-stories/3-second-distraction-doubles-work-errors/ | |||||||
Developer Support Handbook - http://www.developer-support-handbook.org/intro.html In this handbook, I mostly cover the first aspect of providing an API: support. It is probably the least glamorous aspect, but on the other hand, it is vital. You can have the best API in the world, but if people post in your forums and the response is just crickets chirping, then the developers will not stick around for very long. On the other hand, if you treat your developers well, then they will (for free) provide you with valuable insights about ways to improve your API, and they will evangelize your API for you. | ||||||||