add hotspot analysis

[svenjohann]

Adam Tornhill describes hotspot analysis in his book "Your Code as a Crime Scene".

Hotspot analysis is an interesting approach to determine the value of an improvement. It looks at the rate of change of classes by analysing the (recent) commit history and also looks how complex the code is. If your code is complex and it gets changed often, than you have good candidates for improvement. Code which is changed often is better be good, because, from a Technical Debt perspective, the interest is really high if often changed code also smells a lot

[gernotstarke]

+1

Am 10.11.2016 um 20:26 schrieb Sven Johann <notifications@github.com mailto:notifications@github.com>:

Adam Tornhill describes hotspot analysis in his book "Your Code as a Crime Scene https://pragprog.com/book/atcrime/your-code-as-a-crime-scene".

Hotspot analysis is an interesting approach to determine the value of an improvement. It looks at the rate of change of classes by analysing the (recent) commit history and also looks how complex the code is. If your code is complex and it gets changed often, than you have good candidates for improvement. Code which is changed often is better be good, because, from a Technical Debt perspective, the interest is really high if you have to change these parts of the code often

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub #199, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLURvJ8vBkcwwsRXPiFio1FVUBn_slfks5q82_MgaJpZM4KvChV.

https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png https://github.com/aim42/aim42 #199

[gernotstarke]

Sven, is that one really "in progress"?? I'd appreciate if you could add some lines on it...