Imagine you have a colleague named Boris. And Boris has a problem: he's been working on a new feature for five days, but now it's all falling apart. The application starts up, runs for a few minutes, and then shuts down with some weird error message and a huge stack
Jackson is a go-to person when it comes to MongoDB. You have a problem – you go to Jackson.
Some people are lucky to work with extremely smart bosses. Molly hit the jackpot.
Types of people we may unknowingly use as pacers to adjust own behaviour. If you know them, you can control this effect and even change how you affect others.
Introducing the concept of pacers – people who can impact the performance of teams and companies by just speeding up or slowing down.
Although I'm not a big fan of reviewing code together with the person who wrote it, this approach has some benefits. Most importantly, it significantly shortens feedback loops which sometimes can last for hours and even days: This would be very easy to avoid if both the author and reviewer
"Yesterday's Weather" is a popular Agile technique that allows teams to predict future performance. If you estimate, you definitely should use it.