How it works
Reviews
About
Blog
Products
News & Events
Login
Blog
By Adam Tornhill
Communicate the Effects of Technical Improvements to Non-Technical Stakeholders
The Bumpy Road Code Smell: Measuring Code Complexity by its Shape and Distribution
CodeScene joins the GitHub Student Developer Pack
How Healthy is Your Codebase? Introducing Code Health and Biomarkers for Software
Predicting Code Quality Issues Before They Happen: A Minority Report for Code
How CodeScene Differs From Traditional Code Analysis Tools
Visualize Brooks's Law: When More People Makes a Late Software Project Later
Use CodeScene's CI/CD Quality Gates to Manage Technical Debt with Positive Reinforcement
CodeScene 4.0: Dawn of a new User Interface
All articles
Announcement: CodeScene is Free for Small Businesses and Distributed Teams
CodeScene joins GitHub Teacher Toolbox.
CodeScene 3.6: Visualize Team Coupling and Logical Dependencies in the Context of the Software Architecture
CodeScene 3.5: Open APIs and more Predictive Capabilities
CodeScene 3.4: Put Costs on Hotspots and get detailed Code Review Feedback
Under the Hood: Prioritizing Technical Debt in React
How Does CodeScene Compare To Static Code Analysis and SonarQube?
CodeScene 3.3: Change Coupling Trends and Delivery Performance Metrics
Better Than Silver Bullets: A Milestone for Behavioral Code Analysis
CodeScene 3.2 Released
CodeScene 3.1 Released
CodeScene 3.0: Behavioral Code Analysis Reborn
Manage Technical Debt With Augmented Code Analysis
CodeScene: The First Three Years of a Bootstrapped Startup
A Project Management Software that Understands Code
Relevant Retrospectives: Visualize how each Sprint Impacts your Codebase
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
Prioritize technical debt with CodeScene
Release of CodeScene 2.8
Minimize On- and Off-Boarding Risks
Release of CodeScene 2.7
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
