How to rewrite legacy applications or split monoliths into microservices without slowing down on delivering features or introducing bugs in your system.
The need to rewrite whole or parts of your applications arises frequently. Be it a legacy modernization initiative where your organization plans to move from monoliths to microservices, or some parts of your application have become so complex and slowed the development process, that they call for a rewrite.
But this kind of change in software architecture is a big undertaking:
There are a lot of articles on what pair programming is, why it is liked and followed by some people and organizations or why not. This post lists some bottlenecks in pair programming and suggested ways to address them.
A lot of organizations embrace pair programming, or pairing for other tasks for the values it adds:
All things Software Development | Tech Lead @ ThoughtWorks