Predicting Code Quality Issues Before They Happen: A Minority Report for Code
The earlier we can catch any code quality issues, the better.
Our blogs walk you through usecases and show you how to make the most of CodeScene and your code. Our developers share best practices and cover topics less explored, but so valuable to development organizations.
The earlier we can catch any code quality issues, the better.
We’re proud to announce a new release of CodeScene, version 3.4!
Behavioral code analysis is a young discipline.
Static code analysis is valuable in finding code that is overly complex, violates a specific style guide, or contains error prone constructs.
We’re proud to announce a new release of CodeScene, version 3.3!
My work on code analytics started 10 years ago, and the CodeScene analysis tool has been my main focus for the past 4 years.
We’re proud to announce a new release of CodeScene, version 3.2!
Four decades ago, Fred Brooks coined what we now know as Brooks’s Law: ”adding human resources to a late software project makes it later”.
We’re proud to announce a new release of CodeScene, version 3.1!
CodeScene identifies and prioritizes technical debt.
We’re proud to announce a new major release of CodeScene, version 3.0!
Many organizations spend significant parts of their development budgets in parts of the code that are more expensive to extend and maintain than they have to be.
Watch CodeScene run the latest analysis results of your favorite open-source project.
Behavioral code analysis is a young discipline.
Everyone in the software industry "knows" that code quality is important, yet we never had any data to prove it. Consequently, the importance of a healthy codebase is largely undervalued at the business level.
We set out to remove the quotation marks so that "knows" becomes knows. We recently published new research that for the first time quantifies the business benefit of high-quality code. Here are the key takeaways:
Complex code slows down development productivity, increases the delivery risk, and leads to excess maintenance costs.
Tightly coupled microservices are a cardinal sin.