How it works
Reviews
About
Blog
Pricing
Login
Blog
By Adam Tornhill
How CodeScene Differs From Traditional Code Analysis Tools
CodeScene: The First Three Years
How Healthy is Your Codebase? Introducing Biomarkers for Code
Measure Conway's Law with CodeScene
The Cost of Code: Bridging the Gap between Tech and Business
Meet the Branch Measures: A Behavioral Code Analysis to Predict Delivery Risks
Release of CodeScene 2.7
Relevant Retrospectives: Visualize how each Sprint Impacts your Codebase
Prioritize technical debt with CodeScene
All articles
Release of CodeScene 2.6
Release of CodeScene 2.5
Release of CodeScene 2.4
CodeScene in Research
Prioritize Technical Debt in PL/SQL Code
Release of CodeScene 2.3
Analyse Pair and Mob Programming Patterns
Release of CodeScene 2.2
Release of CodeScene 2.1
Early Warnings for Future Maintenance Problems
Release of CodeScene 2.0
CodeScene in your Continuous Integration Pipeline
Release of CodeScene 1.8
Migrating from TFS to Git — How to Run CodeScene on TFS Projects
Release of CodeScene 1.7
Release of CodeScene Enterprise 1.6.1
The Status of Your Code At a Glance
Software (r)Evolution — Part 4: Scale-up - Analyzing Patterns in the Evolution of Linux
Release of CodeScene Enterprise 1.6
Release of CodeScene Enterprise 1.5
Software (r)Evolution — Part 3: Time - The Hidden Dimension of Software Design
CodeScene — Brand and Design
Release of CodeScene Enterprise 1.4
The Day I Parsed A Monster
Release of Empear Enterprise 1.3
Software (r)Evolution — Part 2: Novel Techniques to Prioritize Technical Debt
Software (r)Evolution — Part 1: Predict Maintenance Problems in Large Codebases
Release of Empear Enterprise 1.2
The Happy Marriage of Retrospectives and Software Evolution
Empear Developer Edition with PHP support
Announcing Empear Developer Edition
Take me to the Help Desk
