I often use some tools to analysis my code (SonarQube in my case). They are often a valuable tool for both ensuring my code is of a good quality & for pointing out mistakes I have made (along with how to fix them).
I wasn't quite sure what the best way to present the list of tools were though. Giving each one it's own heading seemed like overkill.
I often use some tools to analysis my code (SonarQube in my case). They are often a valuable tool for both ensuring my code is of a good quality & for pointing out mistakes I have made (along with how to fix them).
I wasn't quite sure what the best way to present the list of tools were though. Giving each one it's own heading seemed like overkill.