Why Pair Programming can be a Nightmare, especially while coding with Typescript?

General thoughts on pair-programming with friendly engineers.

Maybe you have decided to join a team of engineers.

Your Team leader has decided to recommend you try some “Pair Programming” with a peer.

An excellent chance to get comfortable on your new team, contribute to their progress and share knowledge.

However, many don’t understand the dark-side to “Pair programming” and why it can be a nightmare. Well, its not actually dark or bad… it can be rewarding when done right.

First off, I’ve always enjoyed pair programming because it had given me the chance to learn and grow as an engineer, which I had welcomed!

I can easily count on the fingers of my hand the times, I’ve coded with smart people.

Its enjoyable, when you are compatible with your peer and the task at hand is of interest.

The number one reason, why “Pair Programming” can actually be a disaster for your colleagues and yourself is due the possibility of being mis-matched with another engineer.

Always remember, it’s perfectly normal and don’t forget to keep an open mind when in these scenarios.

You may not be able to choose who your peer will be at the start but I recommend in this situation you remain open to learning and avoid being defensive in order to move forward with any tasks or projects together.

You will learn more, if you are willing to change. Everyone has the ability to learn.

Now the for the nightmare in “Pair Programming” really starts when you introduce coding with Typescript.

It is actually, all due Typescript.

Even a seasoned professional not just a beginner in Typescript programming, may have experienced this exact same issue.

It’s partly due to Webpack. Let’s be clear for the folks in the back.

Webpack is a tool used to bundle Javascript for the browser and many Typescript projects will utilize some kind of bundling. Webpack happens a very commmon tool baked into JS frameworks.