I find that there's 2 types of pair programming:
- when you need to move fast, the more experienced person drives
- when you want to teach, the less experienced person drives
The second option can be super frustrating but it's more effective long-term.
The first option is great for picking up on little techniques that the expert wouldn't even think to mention because they're so ingrained you forgot you ever had to learn them. Like jumping around a debugger or git grepping to navigate a codebase.
Always have a goal in mind.
Pair debugging is best. Pair refactoring with a specific outcome is amazing. Pair coding a new feature … eh.
Cheers,
~Swizec
PS: pairing is most effective before you start to code. Start every project with a little system design session and things will go smoother I promise
Continue reading about Pair programming
Semantically similar articles hand-picked by GPT-4
- Coordinating at the end is too late
- Make mistakes easy to fix
- Own the outcome, not the work
- Why senior engineers get nothing done
- When's the last time you tried something new?
Become a *true* Senior Engineer
Get promoted, earn a bigger salary, work for top companies
Getting that senior title is easy. Just stick around. Being a true senior takes a new way of thinking. Do you have it?
The Senior Minset email crash course
Get a free chapter from the Senior Engineer Mindset book and a sample audiobook chapter, followed by a Senior Mindset 101 email course.
You'll get insights to apply at your work right away.
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️