I’m delighted to announce that my agile software development book is in print. While at Pivotal, I earned my Ph.D. by studying what made Pivotal’s teams so successful. It had been 20+ years since the Extreme Programming books had been written and I wanted to share how Pivotal had evolved the XP practices. We knew the practices were successful and my research helped understand the fundamental underpinnings on why it was successful.
Note: This is one part of my journey to tame a spaghetti model or god object. Start with Post 1: Unraveling a Spaghetti Model to see how I chose to tackle this problem.
Note: This is one part of my journey to tame a spaghetti model or god object. Start with Post 1: Unraveling a Spaghetti Model to see how I chose to tackle this problem.
Note: This is one part of my journey to tame a spaghetti model or god object. Start with Post 1: Unraveling a Spaghetti Model to see how I chose to tackle this problem.
Note: This is one part of my journey to tame a spaghetti model or god object. Start with Post 1: Unraveling a Spaghetti Model to see how I chose to tackle this problem.
In many established Ruby on Rails applications, there are often a couple of classes that become entangled with the rest of the code base. These early models start small and simple, possibly present for the first commit, but over time, the rest of the code base becomes entangled with them.
On January 10, 2023, our code base turns 11 years old. For a repo with this much history, we’d expect for the business needs and features to have evolved over time. Surely in the quest to ship new features, our past selves might have forgotten to remove all the dead code. While examining our spaghetti model, we were trying to figure out the purpose of each item. Some of this analysis is waste since the column might be dead code.
While working on a feature or a refactor, sometimes we wished that the code looked differently. A developer might think, “If only the code than this interface or this structure, then my work would be easier.” When this happens, we could either do all the refactorings at once or sequence the work with an Inception Refactor.
Renaming the Scrum Master role. On my team, we’re discussing “scrum facilitator” or “scrum enabler.” I asked twitter for ideas and here’s what you all came up with.
