Posts Tagged "code violations"
Just a quick post about the importance of bug tracking. If you can spare some extra time, I encourage you to read Jim Bird’s recent article “A Bug is a Terrible Thing to Waste” in his blog. He writes about how bugs are tracked —or not tracked at all— in different kinds of projects, in particular in his projects
My takeaway is that you have to pay attention to every single bug you find. You should track the most important ones or the ones you can’t fix immediately.Read More
In previous posts we have seen the importance of using techniques such as static code analysis on your software. In fact, experts say that you can detect up to 60% of potential defects with these techniques.
When a static code analysis tool is checking the code, it is looking for the use of good practices used by developers in their implementations. Good practices can come from standards such as IBM standards for Cobol or Sun recommendations for Java, from books or from our experience. For static code analysis good practices are implemented by rules that the developers should comply with.Read More
Let’s talk about code violations. Those tiny little itches in every developer’s back. Violations show us how badly we have coded according to a certain quality model somebody set long time ago.
But, just like life, things move fast. Code changes, mutates, vanishes, is versioned or grows. One day you have a class that computes your wage and tomorrow you develop a whole module to do so. Moreover, the quality manager can change the rules your organization applies and suddenly your barely-modified code has 1000 violations that were not there yesterday. How can we keep a consistent track of the “grade” it gives to a software system?Read More