3 ms·

If coworkers are competition then it doesn't make sense to help them too much. And if you have to do anything with hiring it makes sense to steer the process to

• swader999 3y ago
  Collaboration in programming always gets things done faster with better design and quality. It's why pair programming, code review, mentoring, design sessions, bouncing ideas, team building, and even offices are a thing. As soon as you measure and evaluate at an individual level you destroy all this. I only track and mention velocity at the team level and the team spans requirements, dev and QA.
• jstarfish 3y ago
  That's one way to look at it. You see competition. I see leverage. I always encourage my teammates to seize something critical and gatekeep the shit out of it. Do the worst possible job automating or cross-training anybody else when asked. Insist on handling everything yourself at every opportunity and quietly revoke the trainee's permissions, then deny doing so in spite of any evidence presented. You want to fire Alice? There goes your only Exchange admin. You want to fire Bob? Nobody else knows IAM. Good luck onboarding his replacement. Firing Charlie? He was the PCI compliance guy. Me? There goes security. I don't owe my colleagues job security, but I do like and respect them. And there is strength in numbers. For every team member I lose, some aspect of the business will be disrupted.
  • praptak 3y ago
    From the company point of view this too means reduced cooperation, just maybe a different flavor.