Posted on by Link Roundupin
In December 2014, Andre Infante of CoinReport wrote about a Bitcoin developer's warning that the rapid development of Bitcoin software may be "introducing consensus bugs." In Peter Todd Warns of Potential for Accidental Bitcoin Forks, Infante describes how the pace and scale of refactoring may have created a fork in the development. If the fork is not corrected, the network may not be able to achieve consensus about official versions of events, which could wreak havoc for a payment system. This link roundup offers several recent blog posts and a conference presentation on the topic of refactoring. Sacrificial Architecture: Martin Fowler of ThoughtWorks, and author of Refactoring, explains why he hopes that in a few years you'll need to throw away the code you are creating today. Architecture Seams: Jean Barmash at Hello FooBar! expands Michael Feathers' term seam from the book Working Effectively with Legacy Code from code to architecture, then discusses how to exploit architecture seams in a large-scale refactoring project.
Refactor vs. Rewrite: Girish Suryanarayana, Girish Suryanarayana, and Tushar Sharma at designsmells.com explain that huge, old legacy software can acquire a body of knowledge that is worth saving. Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work: At the First Israeli Conference on Software Architecture, Joseph Yoder of The Refactory argues that continuous delivery, test-driven development, refactoring, and a long-term commitment to architecture can keep you out of the mud. A video of the talk is available. We are pleased that Yoder will also speak at SATURN 2015, on the topic of "Keeping Core Components Clean While Dealing with Data Variability" in a session called Sustainably Supporting Data Variability, led by Rebecca Wirfs-Brock. Join us in Baltimore at SATURN 2015 by submitting a proposal today!