3 ms·
Since you've explicitly asked for advice, the only way to assess remote employees is by what they're delivering. If you employ them for 40 hours a week, but the
by jon-wood 5y ago
Since you've explicitly asked for advice, the only way to assess remote employees is by what they're delivering. If you employ them for 40 hours a week, but they can deliver what you're asking in 5 and still be responsive when needed, is there really a problem?
If they're also doing another job on the side, but it isn't impacting their delivery of the work you're asking for, that shouldn't be a problem. By doing away with a (largely unenforceable) policy of no moonlighting you also avoid the problem of having to fire people for breaching it.
I'm borderline on whether Alice here was even at fault. She is likely in breach of her contract for several other things, I assume there's a routine NDA in place which probably means that she shouldn't be sharing confidential company information with outside parties, but if not and she was getting work delivered is it really a problem if she did so by being good at project management rather than software development?
- Zanneth 5y agoIt's a really unethical thing to do, and you don't want unethical people working at your company.
- giorgioz 5y ago>assess remote employees is by what they're delivering I agree but that is easier said than done. Software is very intangible and creative and I do not have experience in managing other developers. One of my employees is a university dropout with 3 years working experience from a developing country and is the only developer other than me. I have no clue what's the amount of code he's suppose to deliver. I have very little metrics of reference to work with.