3 ms·
I am still fixing up the code of a developer from five years ago who was there for two years prior to me. He had ideas about how things should work and complet
by shagie 5y ago
I am still fixing up the code of a developer from five years ago who was there for two years prior to me. He had ideas about how things should work and completely disagreed with the conventions of every framework.
And so, every time I go in a section of code to fix a bug or adjust a feature and I see his name in git blame... I spend another few hours to make sure that I'm not breaking some of the twisted framework code that he had and possibly fix it up a bit and adding a unit test for the functionality before I touch anything to assure myself that I know what it is doing.
An unproductive poor employee is bad... a productive bad employee is where the real problems are for years and years to follow.
- Retric 5y agoThe question is how likely a longer interview process with avoid such employees not that they have a cost. In your case code reviews could have caught the issue early before it became such a problem. Though obviously they also have a cost.
- sgtnoodle 5y agoI don't think a longer interview process is strictly necessary to avoid hiring unqualified people. Rather, a longer interview process helps to hire more people while maintaining high standards. Individual interview sessions go poorly all the time for silly reasons. If a candidate only had one interview session and botched it, they're probably done. If they had several sessions and botched one but showed excellence in another, they would still have a good chance of getting an offer.