Timeline for Handling low quality work from a senior
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 20, 2014 at 8:42 | comment | added | Vector | +1 : Going behind someone's back (senior or not) and undoing their work is on the border of unprofessional | |
| Jul 7, 2014 at 22:52 | comment | added | Telastyn | @AndyBursh - you should definitely not just leave the code there. You should "suggest a better solution", which would be easier to do before burning down their hard work. | |
| Jul 7, 2014 at 20:59 | comment | added | Andy Hunt | @Chris That sounds like a good, positive solution. Thanks! | |
| Jul 7, 2014 at 20:53 | comment | added | user9542 | @AndyBursh: No, it's better to address it directly, but as Telastyn said you should talk about the code not about the person. Try to phrase it like you made his good work even better and ask if he agrees or has more suggestions. | |
| Jul 7, 2014 at 20:48 | comment | added | Andy Hunt | @Chris, Telastyn Would you agree that then that allowing him to find out for himself, and being prepared to participate in a code review, is the best approach? | |
| Jul 7, 2014 at 20:44 | comment | added | Telastyn | @AndyBursh - it's probably better than just letting him find out about it himself. | |
| Jul 7, 2014 at 20:36 | comment | added | Andy Hunt | "think they are incompetent and that they're so bad .. that you don't even want to work with them". This is what I feared he would think. I would've liked to try work with him on this, but it wasn't an option at the time. The work is now done and in the codebase. Is it still possible to start a conversation purely about the problem? | |
| Jul 7, 2014 at 16:37 | history | answered | Telastyn | CC BY-SA 3.0 |