But don't documentation and tests help the developer? If I write my documentation first, it makes me think about the API, and because I don't like writing documentation it makes me think about simplifying it. Which is good for my code.
If I write my tests next, it gives me a baseline of correctness. I get to try to write the simplest code possible to pass my tests. Which is good for my code.
I see your point about ease of consumption, and I certainly appreciate it when folks rock an awesome change log. Is there any motivating factor for the developer, other than extra cookies, that you can think of?
-- Douglas Hunter