Release of CodeScene 2.6
We’re proud to announce our 2.6 release of the CodeScene on-premise version!
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.
We’re proud to announce our 2.6 release of the CodeScene on-premise version!
These days it’s probably easier to track down the mythical Yeti than to find a software organization that hasn’t adopted some form of agile practices.
We’re proud to announce our 2.5 release of the CodeScene on-premise version!
We’re proud to announce our 2.4 release of the CodeScene on-premise version!
The CodeScene tool has its roots in my books, Your Code As A Crime Scene and Software Design X-Rays: Fix Technical Debt with Behavioral Code Analysis.
We’re proud to announce our 2.3 release of the CodeScene on-premise version!
When we started developing CodeScene, our overall goal was to show that there is more to code than code; we wanted to highlight–and make actionable–all the information that is invisible in the code itself.
We’re proud to announce our 2.2 release of the CodeScene on-premise version!
The Swedish king, Carl XVI Gustaf, visited our office to see a demo of the CodeScene tool.
CodeScene’s project management metrics let you measure where you spend your costs and how the development activity shifts over time.
Many organizations transition to short lived feature branches and employ practices like continuous integration/delivery.
We’re proud to announce our 2.1 release of the CodeScene on-premise version!
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”.