9 Be a team player

 

“Can’t you just let me write code and leave me alone?” It’s a question I’ve asked more than once (along with “let me run the servers,” “let me build the DevOps pipeline,” and related variants), and it’s a question whose answer is invariably no. Teamwork is an integral part of getting things done in tech, and your ability to be an effective, positive teammate is probably one of the top skills any employer looks for.

9.1 The ups and downs of teams

I will freely admit, now that I’m a bit older and it’s in my past, that I haven’t always been a great team player. If you’ve seen The Big Bang Theory on TV, I’m Sheldon Cooper in far too many ways. You might be a more natural team player, and some of the advice in this chapter may seem somewhat obvious to you. But if you’re like me, the tips I’ll present are things that you have to actively focus on every day and put real effort and energy into.

One of my weaknesses stems from a strength: I’m a “Get things done” worker. Point me at a problem, get out of my way, and be prepared to bury the bodies I leave in my wake. In meetings, I’ll state my views clearly, and I’m often the first one to speak up. That’s the strength. But then I’ll then defend those views to the death, convinced that my way is the best way forward. I want everyone on my team to be on my side and to rally for my idea.

9.2 A checklist for being a better team player

9.3 Dealing with less-effective teams and teammates

9.4 Contributing to an inclusive workplace

9.4.1 Help

9.4.2 Offer respect and support

9.5 Further reading

9.6 Action items