News for hackers. Stuff that matters.
Re:GitHub lost $66M in nine months of 2016 by arctangent on Thursday December 15, 2016 @10:08PM (#13190773)
> Charge daily or weekly, not hourly.

This can work for the provider of a service, in certain circumstances.

But my opinion is that it is always better to charge a price that reflects the value delivered, no matter how long it takes to deliver that value.

There is a (possibly apocryphal) anecdote I read once in which a consultant was brought in to service a machine with many parts. He replaced one part and invoiced (say) $10,000 for replacing a part worth $1. When asked why his bill was so high, he said: "I charge $1 for the replacement part. The other $9,999 is for knowing which part to replace."

As knowledge workers, those who are skilled must remember that "hours spent sitting in a seat" is not a valid measure of their productivity and should not permit clueless managers/clients from judging them in that way.

Re:GitHub lost $66M in nine months of 2016 by dsacco on Thursday December 15, 2016 @11:38PM (#13191110)
Yep, I agree. Part of my philosophy in charging weekly is to abstract away the cost from an hourly metric and anchor it closer to the project itself.