BartWullems's blog is a platform for sharing insights and expertise in Microsoft technologies, software development best practices, and programming tutorials. Through articles, code samples, and technical discussions, BartWullems offers insights into building scalable, maintainable, and performant software applications using Microsoft technologies such as .NET, Azure, and Visual Studio. Readers can learn about design patterns, development techniques, and tooling recommendations to enhance their skills and productivity as Microsoft developers. Additionally, BartWullems provides updates on the latest developments in Microsoft ecosystem, community events, and industry trends to help developers stay informed and engaged in the Microsoft developer community.

The Art of Simplicity

Pair programming offers benefits such as enhanced knowledge sharing, maintaining flow, avoiding waste, and enabling continuous integration. It requires a cultural shift and a commitment to the practice.

Why pair programming should be your default way of working

I will probably get nothing done if I were programming in a pair.

Here’s an honest first-hand experience by a colleague of mine: <a href="https://shiftmag.dev/pair-programming-benefits-challenges-563/" target="_blank" rel="noopener nofollow">https://shiftmag.dev/pair-programming-benefits-challenges-563/</a>

I don’t agree with the “no pull requests or pull request reviews”. One of the big benefits of PR reviews is someone who wasn’t involved in finding the solution looks at the code with completely fresh eyes.
Reviewing code in the pair is marking your own homework…