Just finished reading "Software Design X-Rays". Really interesting book. pic.twitter.com/qzXlVRmmDw— Mario Carrión #LFGM 🍎 (@mariocarrion) May 11, 2018
I was interested in reading this book since I saw the Beta version a few months back, gladly my interest was rewarded and it did not disappoint. It left me with a new way of looking at Software Development and showed me a measurable way to look at bottleneck code and hot spots.
Software Design X-Rays introduces the idea of using your version control system history as a way to detect code that currently is, or could become, a problem to maintain in the long run. It reminded me a bit of Re-Engineering Legacy Software because it covers how to fix legacy code, however the principal difference between them is how to detect the code that requires to be broken down in advance before replacing it; it helps you detect the offending code and whatever we decide to do to replace it is up to us.
Although in “Software Design X-Rays” analysis tools like CodeScene and Code Maat are mentioned the principal tool used for almost all examples is surprisingly
git. That’s what I believe makes this book so approachable, because it is most likely you’re already familiar with
git, so using what is learned from the book is easier to apply. Using
git with different input arguments, depending on the goal we are trying to achieve, we are able to determine code that changes together, code that changes too frequently or code that will be difficult to understand if the principal developer decide to leave.
Those kind of metrics together with your CI steps like testing, linting and minimum code coverage help you determine the overall health of our codebase and guides you during its lifetime.
Cool short read and more importantly, really well spent time.