I am a senior project manager employed at one of the big multi-nationals in India. Though I manage many software projects, I don't write any code as part of my office work - its more about ensuring others in my team do their job well.
The application Code Analyzer was born out of a need to measure LoC after getting too many complaints about one of the modules being very buggy. Though intuitively I felt that the module was big, I didn't find any free tool that would measure the actual lines of code (excluding comments, blank lines) for all the file types used in the module (I am using the word module loosely here - it is a fairly big portion of our product).
With a desire to refresh my knowledge in Java (at my level, I am not expected to be hands-on), I decided to develop a tool myself. That's how the initial version of this tool was born.
In our organization, we used to measure code complexity, because in the past, we had developed notoriously long functions with a complexity of 100+ and there were a lot of bugs in the developed software. The license of the tool which we were using expired, so we stopped measuring complexity. One day, while I was searching the Internet, I came across a free LoC tool called JavaNCSS, which also computed Cyclomatic complexity for Java code. That gave me the idea for enhancing my tool to compute Cyclomatic complexity for all the filetypes used in my projects - C++, Java and VB. So I enhanced my LoC tool for this - in the process, refreshing some of my unused knowledge of lexical analysis and parsing, that had become quite stale over the years.
Since this tool was developed out of my own initiative (nobody asked me to do it) by working over weekends and after office hours, I hold the copyright for it. I have put it up for free download mainly for the benefit of others who may see some use for this tool in their organization.