> Though do the same for bad engineers and you'll get comically disastrous results...
Is there any way to manage bad engineers that does not end in comically disastrous results?
Is there any way to manage bad engineers that does not end in comically disastrous results?
I find giving them smaller, well defined tasks and checking in frequently helps erk some productivity out of them. Also having lots of check-ins and pair-debugging sessions opens the door for a lot of mentoring opportunities. If their still bad, send 'em to tech support or QA! (only kind-of kidding)