I won't say it's great by any means, but I have used QuickBooks just fine in the past. The key thing here isn't necessarily quality though, the point is they use a validity method to determine the source code will compile and by doing it every few minutes they can catch errors sooner. This is great if your source is 10 million lines of code, but they still have to trace out the changes that caused the failure via the coders who developed said changes. That said do the coders not compile their own code to test the same thing before they submit, I mean I launch my code after almost every change I make to ensure compiles and there are no errors/warnings (I'm a bit of an obsessive on this), thus I am doing the exact same thing they are calling great, sure I am typically the only developer but on occasion I am not, and I do like to catch mistakes early, especially while me or the other developers still have the changes fresh in their heads. I don't think Inuit has cornered the market on this method nor does it make a product quality so I am not sure how this technique really is anything out of the norm and makes their practices better than others in large source sets. Hell, I just inherited a new app with lots of deprecated functionality that was never removed and have since I have no knowledge I have been refactoring the code and in many cases commenting large sections out just to see what errors I get. So far I have been able to remove about 12 classes, and the number of lines of code on most pages are typically 1/3rd - 1/8th the original size. Code does exactly the same thing, and in some cases runs faster, get's rid of a lot of unnecessary variables and calls that do nothing other than take up memory and streamline several functions that relied on try catch methods to make a decision to error safe checks. So I want to hear how to improve code by reducing bloat out of 10 million lines of code using some tool for auto refactoring that is amazing because it can find common functionality and refactor them into reusable objects reducing the lines of code and ensuring related processes stay synced in behavior.