2 ms·
I'm confused as for why one would let go a successful employee that worked for 11 months just not to let them work for 12th. Is there some regulation there that
by smsm42 13y ago
I'm confused as for why one would let go a successful employee that worked for 11 months just not to let them work for 12th. Is there some regulation there that significantly changes the cost structure and forces this behavior? Is the change of the cost structure so great that it actually exceeds the cost of constant retraining and the risk of a team completely disintegrating like we witness in the OP article? We're not talking about digging holes there, it takes significant time even for experienced programmer to get into the project and become productive, and the knowledge transfer is always flawed and incomplete even with best intentions, I can only imagine how flawed it is between two "I'm only here for 11 months" people...
- wildwood 13y agoIf the workers are being classified as contractors, then it's important to have an arbitrary cut-off that limits how long they can work at your company. Otherwise some people can get kept on as contractors indefinitely, when they should have been re-coded as full-time employees. Of course, this isn't a limit on length of employment, just a limit on the length of someone's employment as a contractor. Plenty of companies use more of a "contract to hire" approach, and make a decision whether or not to convert employees to full time at the end of the contract.
- smsm42 13y agoYes, I know this model - the company I work for has been using it quite successfully to hire candidates in some cases. But usually it is clear if the candidate is good or not in 2-3 months, so a limit at 11 months and firing successful workers because they reached 11 months and then hiring untrained workers for the same position seems strange. So I wondered what causes such behavior.