loading...

New Devs: Make Pairing a Priority

bekahhw profile image BekahHW Originally published at bekahhw.github.io on ・3 min read

One of the questions I’ve been asked most frequently is also one that I asked most frequently when I first started: “when will I start to feel comfortable, like I’m good enough to be a developer?” One of the most common answers was between eight and twelve months into your first job. And although I think this is accurate, it doesn’t quite get at what I think should be the question: What will help me to be more comfortable as a developer? And while I have a handful of ideas, I think one of the most important things is pairing.

When I taught college English I frequently had complaints about my attendance policy. Why did they have to be there? Because when you’re talking about literature, you aren’t memorizing facts, you’re learning how to talk and grow and to think critically. And the best way to do this is to both discuss your observations and analyses with other people and to listen to other people’s perspectives and approaches. And I think the same thing happens when you’re coding, and it’s one of the things that many bootcamp grads and self-taught devs don’t get the opportunity to do.

At its core, coding is writing and style and communication. You’re communicating with the program. You’re communicating with other developers, project managers, and users. If you can’t communicate your ideas, if you can’t write them in a way that’s logical, then things don’t work or you don’t understand why they work. I don’t think you need a complete, in-depth understanding, but you need to have a sense of why you used this approach for this problem and what this approach does.

Pairing not only forces you to communicate your ideas, but it also gives you the opportunity for feedback, questions, and discussion. One of the biggest challenges when you’re learning to code is you don’t know, what you don’t know, until you know it.

Pairing can be overwhelming when you first start. So here are a couple of tips:

  • Pair with someone who is one step ahead of you. Sometimes this can take the pressure off.

  • Take turns driving and navigating. Sometimes you’ll do the typing while someone else gives you the directions and vice versa.

  • Ask a more senior dev if you can watch them work through a problem.

  • If someone offers to pair with you, take them up on it, no matter how nervous you are.

  • Don’t be afraid to ask for someone to pair with you on a project. It might be their open source project, your project, or something for work. If you have someone you are comfortable with, that’s great. But if you don’t, ask a slack group you’re a part of or even Twitter. In my experience, if someone offers, it’s because they want to help.

I wish I had spent more time pairing when I was learning. Learning to communicate clearly and getting comfortable asking questions was the most important part of feeling like I was a developer. The fastest way I can see to getting there is by pairing or working on a team. It also might look like the scariest, but with a supportive community, there’s only progress.

Discussion

pic
Editor guide