As 2021 draws to a close, we would like to share with you some of the latest features ready and waiting for you in CodeScene. But before that, we would like to take this opportunity to wish you a fun-filled festive season and New Year!
The main difference between CodeScene’s behavioral code analysis and traditional code scanning techniques is that static analysis works on a snapshot of the codebase while CodeScene considers the temporal dimension and evolution of the whole system.
Since starting CodeScene back in 2015, I have probably analyzed around 300 codebases.
Tightly coupled microservices are a cardinal sin.
Sustainable software development is about balancing short- and long-term goals.
Security vulnerabilities correlate with low code health, development hotspots, and a high author churn in the organization.
Our new CodeScene release lets you integrate third party information in the CodeScene analysis views.
Code quality issues can cost time, money, and frustration.
CodeScene integrates with pull requests to provide feedback and detect code quality issues via an automated code review.
Are you one of the 10 million developers who use BitBucket? Then we have some great news for you: starting today, you can analyze your BitBucket repositories via CodeScene Cloud.
A codebase under active development is a moving target that’s going to change over time.
This article shares my experience with the Code Health concept, and explores how it supports both developers and technical leaders with a continuous feedback loop for engineering decisions based on data.
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.
