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

I am the OP and the way this normally works is that we would speak out if someone did something in the wrong way, for example a step in a process was forgotten. It’s better to step in (ha) and help out and make the suggestion of how to fix it.

But to write out constructive feedback which goes against your colleagues record, so that they have to show how they received this feedback and the steps they did to remedy it, seems a bit much.

For example, how do I know that a certain piece of feedback might be really difficult/impossible for you to fix and then you lose out on a %age salary increase or promotion because of it?

I can’t write ‘mr x could really work on coming to work earlier’, as that’s not my job. What if I write ‘mr x. would have been better to use x pattern in his development because ...’, as that would mean I have oversight of how they are doing their work and I haven’t spoken up in time. Which seems crazy.

If you are doing something wrong or something that can be improved, I would prefer to tell you point in time, and when the context is right.

To leave ‘constructive feedback’ against your personal record removes a lot of context, and has the potential to damage your career and our relationship.

I don’t like it!



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

Search: