Most of the time, spending time to reduce the unintended technical debt of a project is a wishful thinking that will rarely come true. Teams prefer to focus efforts on functional & intended debts rather than correcting a bunch of code violations, even if they’re major or critical. However, like any other debt this unintended debt (basically, FindBugs, Checkstyle or PMD violations) generates interests: that is to say an additional cost to maintain the application or add new functionnalities.
Watch this video tutorial and learn how to simply write off your Technical Debt with Scertify, by using its Computer-Aided refactoring features.
In this video, we analyzed and refactored a component of Hibernate, following three steps:
Comments are closed.