3 ms·
If nothing else, I'm thankful to Zach for a lot of the guidance he's provided on his blog over the years. When we did a "field trip" to Github thanks to Scott,
by coderintherye 12y ago
If nothing else, I'm thankful to Zach for a lot of the guidance he's provided on his blog over the years. When we did a "field trip" to Github thanks to Scott, I shared Zach's quote with the engineers here:
"We’re currently at 35 employees and growing, and this approach still works great. But managers love to assign hours for a reason: it gives them the illusion that hours can measure performance.
If you don’t go hard on hours, you do have to look at different metrics. How good is their code? Are they fixing bugs? Are they involved in work, or is the greater flexibility not motivating them?
It’s difficult to make these qualitative judgements, but they’re still going to be more valuable than “did this guy put in his ten hours of work today”. Because as soon as you make it about hours, their job becomes less about code and more about hours."
4 years ago a lot of us had just come to Kiva from corporate gigs and such and were building a culture of meritocracy rather than bureaucracy and even though this advice seems obvious now, they were truly inspiring words at the time. Thanks Zach for all the writing!
- icefox 12y agoHow is Kiva after the Amazon acquisition?
- nowarninglabel 12y agoDifferent Kiva, http://www.kiva.org http://www.kiva.org :)
- curun1r 12y agoJust to add a similar sentiment, I've also seen Zach speak at conferences and his talks are excellent. If nothing else, someone should hire him to represent them at various tech conferences to improve their reputation and attract better talent. And given how insightful his talks are, I'd bet he's at least a decent developer too. I have no doubt that the offers will roll in, despite any stigma over being fired. As someone who hires developers, I'd have no qualms about hiring him.