Replacing Humans with Software Inspectors
An anonymous reader writes "What if you were able to perform a portion of your code reviews automatically? In this first article of the new series 'Automation for the People', development automation expert Paul Duvall begins with a look at automated inspectors like CheckStyle, JavaNCSS, and CPD. The piece examines how these tools enhance the development process and when you should use them." From the article: "Every time a team member commits modifications to a version control repository, the code has changed. But how did it change? Was the modified code the victim of a copy-and-paste job? Did the complexity increase? The only way to know is to run a software inspector at every check-in. Moreover, receiving feedback on each of the risks discussed thus far on a continuous basis is one sure-fire way to keep a code base's health in check automatically!"
...welcome my new automated, software-inspecting overlords.
playmoney.me - The free alternative to paper board game play money
"Go away or I will replace you with a very small shell script."
In Soviet Russia, something inspects something, and it's really funny!
stuff |
If only we could run CPD (copy/paste detector) on /.
I bet the numbers would be off the charts!
I totally agree. I like to compile my projects by hand sometimes just to make sure I'm not reliant on my C compiler.
http://packages.debian.org/stable/admin/vrms
Virtual Richard M. Stallman
The vrms program will analyze the set of currently-installed packages on a Debian GNU/Linux system, and report all of the packages from the non-free tree which are currently installed.
Future versions of vrms will include an option to also display text from the public writings of RMS and others that explain why use of each of the installed non-free packages might cause moral issues for some in the Free Software community. This functionality is not yet included.
Person A: Hey, did you hear about the new version of Eclipse that just came out? It's got this nice feature where...
dpbsmith: Oh, good, the silver bullet at last. We've experienced those brief and tempestuous infatuations with flowcharts, Warnier-Ott diagrams, top-down programming, structured programming, Jackson structured programming, source code control, the waterfall model, Royce's Final Model, the spiral model, the sashimi model, object-oriented programming, CASE tools, Rational Unified Process, SEI's Capability Maturity Model for Software, SEI's CMMI, feature points, function points, agile methodologies, and Extreme Programming, and... well... they were just trips to the moon on gossamer wings.
But this. This is different. Totally different. It's the real thing this time.
Person A: Uh, I just wanted to talk about code folding, dude. Put down The Mythical Man-Month for a while, OK?