3 ms·
If you don't have your existing coding team involved in the interview process for new people, then you are looking for trouble. The net cause is either your own
by contingencies 14y ago
If you don't have your existing coding team involved in the interview process for new people, then you are looking for trouble. The net cause is either your own poor processes and resource allocation (ie. bad hire) or weird internal procedures/standards (overwhelmingly difficult for newcomers to grapple with).
Anyway, '10x your tier of productivity'-style elitism is pointless. People will always either accept new colleagues or get shirty ... there is no objective metric for the infinite range of potential human foibles.
That said, removing someone too early could easily prove a loss ... often people who think differently are a 100x asset. If you can influence an important resource allocation decision with interesting information, then saving both a month's time and the potential alternative productivity for a bunch of fellow developers could easily pay for a hire's first few.
Software's complex, mmkay. Humans are even worse. Chill, we are all flawed creatures :)
</first-bottle-of-red>