4 ms·
It's not great, but I think the real question is twofold. Is the programmer far enough in their career to have been expected to already learn this lesson and d
by Verdex 4y ago
It's not great, but I think the real question is twofold. Is the programmer far enough in their career to have been expected to already learn this lesson and did the programmer in fact learn the lesson.
If they're young and they never do it again, then I think it would be fine to keep the hire. If they keep on doing it, then it's time to go. If they're 25 years into their career, then they should almost definitely have known better.
- gnulinux 4y agoIsn't this a bit backwards? I expect a new hire to understand that they can't put all their initiatives into the product, certainly not a joke, unless they're explicitly told otherwise. I'd expect a new hire to understand there is a natural pace for everything to grow -- as in all relationships -- so they can't go all out on day 1. On the other hand, I'd want a senior engineer to use their initiative a lot more often. They would also understand that their job is to contribute confidently to the best of their ability.
- pvg 4y agoYou won't end up with many senior engineers using their initiative if you beat it out of them before they get to being senior engineers.