Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

But how do you encourage people for difficult tasks? It is easy to commit myself to correct a particular spelling in a lable by tomorrow. But to fix the indeterministic bug that crashes our top client's server every now and then?


It is like metric driven development is a bad idea ...

As soon as any "oh this wont be used for your yearly review" metrics are made up. You need to drop everything and play by the metrics.

I guess a commited to completed ratio encourages padding out the estimate on easy tickets and punnishes doing hard tickets.


You could commit to something like, "Investigate the logs for two hours" or "inspect memory dump" for an hour. From there, one can add more detailed tasks.


Nothing. There is also nothing to encourage people from not taking forever. This metric worked well on my team until I got people who game it by pulling easier tickets and then sitting on them for a week. We still use the approach though. No approach survives a bad team. I could implement draconian rules, but that would just hamper the productive people.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: