We’ve all been there. A system is running, paying its keep, but creating head-aches everywhere. Soon enough there’s enough people thinking that the system must be re-written and a long, and arduous project starts with the aim of re-writing the system from scratch. We know the features that must be in, so it can’t be that hard, right? Wrong! In this episode we review the many anti-patterns that are triggered when a system re-write project is started.
In this episode we refer to the Promiscuous Pairing paper by Arlo Belshee where he describes the principle of the least qualified implementer.
About Paolo D’Incau
Paolo is a passionate agile developer. He spent hist first years of “agile” learning the technical practices but with time he understood that people, culture and values always come first.
Paolo practices and recommends the adoption of eXtreme Programming. In the projects he has worked on so far he has experienced the benefits of building small and big systems adopting practices such as Pair Programming, Test Driven Development, Continuous Delivery and infrastructure automation.