[Hermitian909]

Still happens. I work in a codebase that is definitely on the upper end of complexity for the industry. ~18 months ago we hired a very smart developer who had one of the more rapid onboardings to our codebase I've seen, he was very productive in under a month. It turned out he was too productive and people were starting to find new layers being added to the code base. A few of the more senior folks had to come in and shut him down.

[zx8080]

> shut him down.

Does this mean firing him?

[Hermitian909]

No, it means helping him understand how certain types of contributions he makes are perceived by engineering leadership and giving him access to mentorship that would help him better channel his efforts in ways that would be seen as more productive and something to be rewarded.

If, over time, he continues to introduce more problems than he solves then he might be managed out but I'm hopeful that won't happen.