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.
“Every story is an opportunity to refactor” - Todd Sedano
See k8s run.
Run k8s run! ™
- Todd Sedano
“Requirements” is a pre-agile construct based on our false belief that building software was somehow like the construction of buildings.
Hi. I have come to love Pair Programming. I enjoy the collaboration, cross-training, and better solutions that emerge while I pair.
In my software development practice, I rely on several techniques for increasing the probability of success with a pairing relationship.
Since pairing is a relational practice relying on imperfect communication, misunderstandings and slights can emerge.
There are several ways in which Sustainable Software Development has evolved from Extreme Programming (XP)