Our 300th rule has been released

We are pleased to announce that we have now finished our 300th rule in our MB-Precise Sonar plugin for Websphere Message Broker/IIB.

This week, we added the 300th rule to our plugin that helps you automate your code reviews and find bugs and coding issues in Websphere Message Broker/IIB code (the plugin analyses ESQL, XSL, message flows and mapping nodes).

And the 300th rule was, well, honestly not very exciting.

It was all about spacing. Making sure that the developer had left space between different sections of the code to make it obvious where the logic was.

It had the (very exciting) title - "The ESQL code is not formatted correctly (WMB)"

So, not going to save your company a million dollars.

But it might save you a 20 minute conversation with one of your developers around "can you add another blank line around line 56 as it just makes it easier to read and understand your code".

"But tech lead, why does it matter if it's just a blank line?"

Why indeed ?

There is a a lot of anecdotal evidence that developers spend a lot of time reading code and what sometimes makes it really, really hard is that it's often someone else's.

Some articles have referred to a 10:1 ratio.

So if you are spending 90% of your time reading some else's code, then anything that they can do which makes it easier (for you) is going to save you time and hence your organisation money.

Well ok. Maybe it will save you a million$. - just not today :(

For a full list of the rules we have is available, or to find out more about our product offerings, please refer to our website - www.bettercodingtools.com