Measure Conway's Law with CodeScene
Mel Conway’s astute observation that an organization’s communication structure should be reflected in the software architecture has received plenty of attention over the past years.
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.
Mel Conway’s astute observation that an organization’s communication structure should be reflected in the software architecture has received plenty of attention over the past years.
We’re proud to announce a new release of CodeScene, version 4.1!
Bad code tends to stick.
We’re proud to announce a new release of CodeScene, version 4.0!
No tool will ever save an organization, but situational awareness might.
These are difficult times for many organizations.
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.
Complex code slows down development productivity, increases the delivery risk, and leads to excess maintenance costs.
We’re proud to announce a new release of CodeScene, version 3.6!
We’re pleased to announce that CodeScene is included in the GitHub Student Developer Pack.
We at Empear make heavy use of CodeScene ourselves.
We’re proud to announce a new release of CodeScene, version 3.5!
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.