Prioritize technical debt with CodeScene
Bad code tends to stick.
Bad code tends to stick.
No tool will ever save an organization, but situational awareness might.
This article is a guest blog by Egil Østhus, CEO of Bricks Software AS. Bricks is the company driving the open source feature management system Unleash.
We’re pleased to announce that CodeScene is included in the GitHub Student Developer Pack.
We at Empear make heavy use of CodeScene ourselves.
The earlier we can catch any code quality issues, the better.
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.
My work on code analytics started 10 years ago, and the CodeScene analysis tool has been my main focus for the past 4 years.
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”.
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.
Security vulnerabilities correlate with low code health, development hotspots, and a high author churn in the organization.
Complex code slows down development productivity, increases the delivery risk, and leads to excess maintenance costs.
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”.
