SE-Radio-Episode-253-Fred-George-on-Developer-Anarchy

Origins

Fred George introduces the concept of Developer Anarchy, a radical approach to software development that eliminates traditional management structures. At its core, it empowers programmers by setting business-level goals and allowing them to creatively solve problems without managerial interference 1. This approach originated at Forward, where George observed that removing managerial constraints led to rapid innovation and significant financial success 2. He notes, "We were just making money," as the programmers were given the freedom to explore and implement their ideas 3.

   

Principles

Developer Anarchy aligns with agile principles but diverges in practice, emphasizing rapid deployment and continuous experimentation. Fred George explains that traditional agile practices like story prioritization and iteration planning become obsolete when deploying code multiple times a day 4. He describes it as "extreme agile," where the focus is on fast feedback and minimal planning horizons 5. The approach thrives in environments where microservices enable swift deployment, though George asserts that Developer Anarchy can exist without them, provided there is a mechanism for fast feedback 6.

   

Challenges

Implementing Developer Anarchy presents challenges, particularly in organizational change and team dynamics. Fred George highlights the "sandwich strategy," where both C-level executives and developers support the change, while middle management may resist 7. He notes that many managers left during transitions, but the environment attracted top talent eager to work in a manager-less setting 8. George emphasizes that Developer Anarchy suits fast-feedback environments, where teams can quickly test and iterate on ideas, minimizing the time from conception to execution 9.