At my current job, we use Sonar. I have no idea of it's value "at the enterprise level", or how you might sell it to manager types, but as a developer who uses it, I have mostly positive impressions of it.
My one complaint is that it's configured with a lot of rules I disagree with. These rules were configured by my manager, so it's not really the tool's fault, but the tool still is a part of the process. Some examples of rules I don't like: - all inline constants are flagged as "magic number" violations. - it demands unnecessary getter/setter methods on every property (rather than just public fields) - "Unnecessary Local Before Return": Often I use an extra local variable to make a complicated piece of code a little more readable, and easier to step through in a debugger. On the positive side, it flags a lot of genuine problems that I see in coworker's code. Not all bad code gets flagged, but it does a good job at catching a lot of problems. On Apr 24, 10:49 pm, Eric Winter <[email protected]> wrote: > We are using it on my team which is composed of a half dozen > developers in a company with hundreds of developers. We see value at > the team level. What is the value at an enterprise level? > > I am planning on presenting sonar to our leadership in hopes of > getting some traction there. I think it could really help focus us > and our leadership on the quality and maintainability of our code. > > Thoughts? > > Cheers, > Eric -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
