For the past 3 months, I've been consistently pair-programming with my CTO.

Here's how it started, the progress, and what I've learnt along the way.

🧵

I'd always been vaguely interested in pairing, but it wasn't something we really did in my first job.

My interest was piqued by this (oh so timely!) tweet from James, a week before I started my new job:

https://t.co/qaG81P1osT

2/13
In my onboarding, I mentioned this to my CTO and he was open to giving it a go.

We decided to incorporate it into our workflow and agreed to slack each other whenever we wanted to pair.

However, this did not go to plan.

3/13
Neither of us were in the habit of pairing and honestly, I had so much imposter syndrome around being hired that I was hesitant to ask because I didn't want to reveal how "terrible" I was.

(I moved from a largely HTML/CSS role to a full-blown React/Redux environment.)

4/13
Two weeks went by with little pairing.

In my week three one-to-one, I finally mentioned my struggles with the massive codebase & the panic I was feeling.

My CTO immediately came up with a game-plan, and we formally scheduled two weekly pairing sessions henceforth.

5/13
The relief I felt about how it was handled was palpable.

https://t.co/bPZtxyk78W

6/13
As the weeks went by, we've gotten more comfortable pairing with each other.

For a while, our two scheduled weekly pairing sessions turned into four, as we started to ad-hoc slack each other to work together beyond our scheduled times.

7/13
We'll pair on fixing bugs, implementing feature work & sometimes have mini-learning sessions.

For example, we're slowly transitioning our codebase to TypeScript. My CTO talked through what he's done so far, his learnings, and next steps.

I usually ask a million questions.

8/13
POSITIVES:

I've been able to familiarise myself with the codebase much faster, ask questions, & assimilate many of my CTO's workflow habits.

I've learnt small VSCode tricks & really started to appreciate the importance of reading documentation.

It also fostered teamwork.

9/13
NEGATIVES:

It requires a certain amount of vulnerability to pair with someone much better. I want to show my best, but constantly feel "stupid" for not knowing or forgetting things.

Luckily I don't get treated as such, however, it's an internal battle I face each time.

10/13
For the most part, it's also currently a one-way stream because our levels are so different. (However, I once helped solve a CSS issue and made it even better than it was... that felt awesome!)

Would I suggest adding pairing into your workflow?

Absolutely!

11/13
I'm more comfortable with it now and have since paired with other devs to help them out. Plus, you both get to practice speaking the language of your craft.

If you use Mac, I highly recommend @tuple for pairing. The team has done an amazing job with it!

12/13
Hopefully, this has shed a bit of light on what pairing involves.

For the complete story and a super awesome Pair-Programming Guide, here's the full article on @hashnode

https://t.co/WDlTecX9bK

/end

You May Also Like

The entire discussion around Facebook’s disclosures of what happened in 2016 is very frustrating. No exec stopped any investigations, but there were a lot of heated discussions about what to publish and when.


In the spring and summer of 2016, as reported by the Times, activity we traced to GRU was reported to the FBI. This was the standard model of interaction companies used for nation-state attacks against likely US targeted.

In the Spring of 2017, after a deep dive into the Fake News phenomena, the security team wanted to publish an update that covered what we had learned. At this point, we didn’t have any advertising content or the big IRA cluster, but we did know about the GRU model.

This report when through dozens of edits as different equities were represented. I did not have any meetings with Sheryl on the paper, but I can’t speak to whether she was in the loop with my higher-ups.

In the end, the difficult question of attribution was settled by us pointing to the DNI report instead of saying Russia or GRU directly. In my pre-briefs with members of Congress, I made it clear that we believed this action was GRU.