At last month's meeting Brandon asked about tools that help you manage code complexity.
I mentioned Adam Tornhill's books "Your Code as a Crime Scene" [1] and "Software Design X-Rays" [2]. Somebody asked me to send the info to the list, so here we are... I've got both, but not read the second one yet. They sprung to mind for Brandon's question because Adam is into using version control history to identify hot spots in your code base. The first book comes with some open source code for putting his ideas into practice, and analysing your git logs. [3] Maintenance is expensive because changing code is hard, and it makes sense to invest some effort in making that maintenance easier. Unfortunately, we don't know when we're adding a new feature whether or not we're going to need to do much work on it in future. And many of us are tempted to make *all* of it easy to change. Adam's big idea is that writing good code by default is a waste. He's developed techniques to identify areas of the code where you see a positive return from investing the effort. He goes into detail on that in [4]. Cheers, Graham [1] https://pragprog.com/titles/atcrime2/your-code-as-a-crime-scene-second-edition/ [2] https://pragprog.com/titles/atevol/software-design-x-rays/ [3] https://github.com/code-as-a-crime-scene [4] https://www.adamtornhill.com/articles/code-quality-in-context/why-i-write-dirty-code.html -- You received this message because you are subscribed to the Google Groups "North West Ruby User Group (NWRUG)" group. To unsubscribe from this group and stop receiving emails from it, send an email to nwrug-members+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/nwrug-members/8c447906-33a1-4b15-8fbe-090a34bd359e%40betaapp.fastmail.com.
