Tech Lead Handbook

Tech Lead Handbook — Pair Programming

The What

Pair programming to exchange knowledge among people

Pair programming to the rescue

The How

For Ramping Up New Team Members (effective)

For Upskilling Juniors (pretty common)

For Firefighting (it’s a must)

  • ClickOps
  • Deploy the latest working image on your dev machine
  • Run SQL scripts to fix broken tables
  • Run shell scripts to fix a broken node

To unblock yourself or your colleagues (do it)

Troubleshoot Defects (can be helpful)

Avoid Bugs (okay but costly)

🔴 Red Flags

  • Paring can be exhausting.
  • Pairing doesn’t work for everyone
  • 100% pair programming can harm productivity and responsibility. Don’t do that.

📜 Tips




Software Engineer | Technical Lead | Engineering Manager

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

What is Memcache & How to use in PHP

Flow-typed might have been a mistake

A Guide to JPA with Hibernate (Relationship Mappings) — OneToOne , OneToMany , ManyToOne …

Laravel Tip: Testing your emails contents

Make virtus gem dry to speed up Ruby app API

Flutter is All-rounder

Installing Istio on AKS

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jamie Wen

Jamie Wen

Software Engineer | Technical Lead | Engineering Manager

More from Medium

Modern Patterns in Software Delivery

Legacy software series — Part 2— Software life cycles and software aging

Summary of What I learned in Design Pattern: Facade

Is Test Driven Development Really Worth it?