From fc3335be83f4e3e38b4f2d0c1ff3d84f1dc09ec8 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Wed, 3 Jan 2024 20:00:00 +0000 Subject: [PATCH] Add daily email for 2024-01-02 Flexible Mob and Pair Programming --- source/_daily_emails/2024-01-02.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 source/_daily_emails/2024-01-02.md diff --git a/source/_daily_emails/2024-01-02.md b/source/_daily_emails/2024-01-02.md new file mode 100644 index 00000000..977a41d7 --- /dev/null +++ b/source/_daily_emails/2024-01-02.md @@ -0,0 +1,25 @@ +--- +title: Flexible Mob and Pair Programming +date: 2024-01-02 +permalink: archive/2024/01/02/flexible-pair-programming +snippet: | + Have you ever asked a colleague to review code you're writing or help you fix a bug? + That's pair programming. +tags: + - software-development + - pair-programming +--- + +Doing pair or programming doesn't mean you need to be working in groups continuously. + +If you've asked a colleague to review the code you're writing or help you fix a bug, that's pair programming. + +You don't always need a driver and navigator, a set rotation time or dedicated allocated daily pair programming time. + +While that works for some teams, and on some occasions, you can do what's needed or feels right at the time to complete the task at hand. + +If you need a short pair programming session to fix a bug or finish a feature, to review some code before you merge it or submit it for code review, or want to pair ad-hoc or for one afternoon a week, that works, too. + +There isn't one way to do pair or mob programming. + +Do what works for you.