Code quality is a big deal.  If developers just try to get things done without proper quality, you will be in a serious bind within a few months.  Each piece of code will be terrible to trouble-shoot, and contain more than the usual amount of bugs. Eventually you will hear the dreaded words from your crew: "It's time for a re-write."

Why not grade your code to see what's really there?  You might think your developer is making great code, but how do you know they are? It's a huge concern for anyone spending their precious resources on building something that is largely invisible.  See, the code produced might never be seen by your users, but that doesn't mean it's unimportant.  Rather, what is hidden could very well be the most important.

Code produced by Bixly is brought to light via the metrics. Of course your can always take a look at what's there, but more importantly, we continually grade the code with various metrics.  They give you amazing insight into how good the code is.  Here is a quick overview of the metrics you will see on your project:

Cyclomatic Complexity

Most programming is actually in reading of code.  If the code is hard to read and comprehend, trouble will arise.  This measurement tells us how complex the code is in your project.  Anything above 7 is considered complex, in most cases.  If you score above 7, it's important that you are aware, so that you can take actions to keep things clean. Read more here.

Braithwaite Correlation

Well, this one is extremely mathematical and hard to summarize.  Most importantly, if your code scores above 2, it shows that the code is clean and can be worked with on efficiently.  To fully understand this metric, get your math degree and take a read.

Unit Tests Pass/Fail Ratio

In this pie chart you will see a simple metric: How many unit tests passed or failed. For those who are unaware, unit tests are little pieces of code that, when ran, guarantee that your code works the way it was designed.  It's a way to spend a little more time up front to reap huge dividends later on in the project.  If all your tests have passed (and you have decent code coverage) you can sleep well at night.  If a bug pops up, write a test for it to make sure it never pops up again unnoticed.   We treasure good sleep.

This is our very first go at showing metrics on your code. We will have more metrics to prove our quality every time.  That's crucial. While our competitors say they have "great quality!", and they very well might, we have taken the steps to prove continually that you are getting fantastic code.