News for hackers. Stuff that matters.
Re:Eric Lippert is leaving Microsoft by MattRogish on Thursday November 29, 2012 @01:01PM (#4849176)
I'm a big +1 for static code analysis as a "silent observer" of code practices. We have various static checks run on each build and if a certain threshold is crossed, the build will kick out an error (we've decided not to have it fail entirely, although some could argue that's a reasonable thing to do).

Although we're a Ruby and JS shop, we take advantage of different services and libraries that perform different checks. In dynamic-language land it's a lot harder to do some of the things that static complication provides, but it's a heck of a lot better than nothing!

There are no comments on this comment yet.