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

I used bad performance to define:

Not doing their job which is tickets assigned them (coding, testing, building, buying groceries etc.)

So we do have a clear definition of what needs to be done, and it's also clear that who's doing it and who's not. Only question in here might what's the accepted amount of tasks done. Like does this ticket takes an hour for X and a day for Y. In either case (Y is slacking or it takes a day for him) he's an incompetent employee and needs to go. Am I missing something?



Like does this ticket takes an hour for X and a day for Y.

Out of context, comparisons like this are meaningless. Maybe the ticket took a long time for Y because he was assigned 30 tickets and spent most of the day suffering paralysis of choice, maybe that particular subject is difficult for him but he has other strengths. When you blamed him for it his knee-jerk response was to get defensive and make excuses (eg personal life problems).


Either way that shows that the employee is not good, if a person can't handle to do his/her own tasks one by one that person should not be work as a developer. BTW generally assigned person decides how long will it take to finish a task (a task can't take longer than 4+ hours if it's needs to be split into smaller chunks)




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

Search: