2025 Public Training Schedule
January 14 – 17, 2025 – Agile Analysis and Design Patterns – Half-Day Sessions
Follow me on Twitter:
Blog Post Categories
- Announcements {19}
- Articles {2}
- Bits and Pieces {74}
- Blogosphere {1}
- Bonuses {2}
- Build in Small Batches {27}
- Collaborate {38}
- Create CLEAN Code {34}
- Implement the Design Last {11}
- Integrate Continuously {30}
- Off-Topic but Interesting {3}
- Rants {82}
- Refactor Legacy Code {24}
- Say What, Why, and for Whom Before How {22}
- Seven Strategies {38}
- Specify Behaviors with Tests {17}
- Write the Test First {27}
Archives
Privacy Policy
(c) 2024 To Be Agile
- April 27, 2016 ( 2 comments )
- Bits and Pieces
Ten years after the Agile Manifesto was signed into being, the original authors got back together to review the progress made in the last decade. It was Jeff Sutherland who said, “Demanding technical excellence is a top priority for the next ten years.”
But what is technical excellence? Given the state of the software industry and the lack of maintainability that most software’s produced with, I think it’s fair to assume that most of us don’t really know what “technical excellence” means when it’s applied to software.
Given that over 80% of the cost of software happens after its initial release, I would propose that a key aspect of technical excellence is being able to deliver software that is maintainable. I’ve asked developers what they do to increase the maintainability of their code, and often got back blank stares.
Maintainability of software is not a subject that is discussed in any depth in computer science curriculums or even in professional software development circles. As an industry, we’re just starting to become aware of the importance of writing maintainable software.
The nine practices I propose in my book, Beyond Legacy Code: Nine Practices to Extend the Life (and Value) of Your Software, support the creation of maintainable software. When not only adopted but understood, these nine practices help us rapidly build maintainable software.
I propose that the core of maintainable software comes from practice five: Create CLEAN Code.
CLEAN is my acronym for five key code qualities that support maintainability: Cohesive, Loosely coupled, Encapsulated, Assertive, and Non-redundant. These certainly aren’t the only qualities we can look at, but they represent a set of code qualities that are easiest for most people to recognize and understand. I won’t go into detail of each of these qualities here, since I cover them in depth in my book, but though these qualities seem simple, almost trivial, we find that when they aren’t present in code, that code becomes difficult to work with and extend.
By paying attention to code quality and building testable behaviors, we can build software that is better adapted to the needs of the user and that’s easier to work with in the future.
{2 Comments }
Previous Post: « The Iron Triangle
Next Post: Scrum Master Toolbox Podcast »
You will enjoy this post I ran across the other day.
https://thinkfoo.wordpress.com/2016/04/29/can-continuous-delivery-succeed-where-agile-has-failed-before/
Great post. Well said!