Pair Programming FTW

Over the last few weeks our modules have centered around programming languages, giving us a lot of opportunities to explore new languages and more time with each other to practice. We were introduced to Katas, using CodeWars.com, and have spent a majority of our time checking out and solving different sample problems. It's cool because you can practice problems in virutally any language you can imagine and you can select problems from varying levels of difficulty.

With the addition Code Wars to our tool kits, we started a new learning method; Pair Programming. We can practice the Kata on our own, but we have been going through them together, too. We've partnered up for small groups and we've also worked through some exercises as a class. I've been able to learn so much from this process and it's definitely something I want to incorporate into my routines to stay sharp on the technical skills while learning new ones.

I was challenged to work through problems in Java and Ruby. Two languages I have never learned or had any experience with to date. It was cool to see some similarities in syntax and methods while seeing a lot of things for the very first time. It has been cool, but also a little overwhelming at times, but I think that feeling can be constructive at times and can be another opportunity to learn ways to improve.

While I found a lot of value in working through problems together as a class, it was a little nerve racking for me. When my anxiety is high I definitely don't absorb as much as I can in a relaxed state. There were many sources of anxiety; not knowing the language we were using, screen sharing, public speaking, being timed, and reading comprehension.

I didn't put pressure on myself to find solutions for these problems, or drive, but I was frustrated with my limited ability navigate. This showed me that I need to improve my technical communication skills and some emotional regulation in situations with heightened pressure.

Reflecting on live and timed exercises in pair programming, I can see the aspects that I will likely experience IRL and to varying degrees. I know there will be many situations, especially in my first few years, where I'm thrown into a project where I don't know the languages being used. It will be important for me to ask the right questions upfront and that's something I need to work on from both a technical perspective but also in terms of my ego and insecurities in social situations.

I think the best way I can work on these things is just continuing to practice. Incorporating Katas in my learning routines, ask questions about how to ask questions, and seeking opportunities to do more pair programming.

The positive outcome of pair programming can be anything from creative solutions to conserving resources to team building. It's all good stuff, but only if the communication is good. I think poor communication would yield the exact opposite results, creating a lot of frustration and tension, diminishing a product's value or a team's productivity. That said, I think the benefit of pair programming is well worth the risk in most cases.