Legacy C application – Refactoring or reengineering? (III)

We continue our series about estimating the costs of refactoring or reengineering a legacy C application. Would you say that the most complex programs and functions also have the highest number of violations to the best practices about readibility and undestandability ?

Enjoy!

Legacy C application – Refactoring or reengineering? (II)

We continue our series about Legacy C applications and how to proceed when deciding about refactoring or reengineering. In this post, complexity and size of functions an programs.

Enjoy!

Legacy C application – Refactoring or reengineering? (I)

We continue our series about Legacy C applications, with the example of the first release of Word (1.1a). Imagine that you have to recommend a strategy for such an application. How would you proceed?

Enjoy!

Audit of a Legacy C application – Microsoft Word 1.1a (II)

Second post of our series about analyzing the source code of Word 1.1a. In this one, I will have a look to the compliance to best practices and the kind of violations that can be found.

Enjoy!

Audit of a Legacy C application – Microsoft Word 1.1a (I)

Microsoft has released this week the source code of Word 1.1a (1990) and I did analyze it. I was curious to see what would be the results, both in terms of quantitative metrics (size, complexity, documentation, duplications, etc.) and qualitative numbers (violations of best programming practices). Also, what would be the technical debt on this software.

Note that I am not looking to debug this Word release so I don’t need the best precision in my analysis. I just want to get an overall view of its quality and think to what can we learn from all of this.

There will be serveral posts. Here is the first one:

Enjoy!

PL/SQL analysis with SonarQube – Evaluating the quality (3/3)

Last post of our series about analyzing PL/SQL code with SonarQube. How to use Technical Debt and the SQALE plugin for an action plan.

Enjoy!

PL/SQL analysis with SonarQube – Evaluating the quality (2/3)

A new post, continuing our synthesis of the current series about analyzing PL/SQL code with SonarQube. How to (quickly) evaluate the quality of an application?

Enjoy!

PL/SQL analysis with SonarQube – Evaluating the quality (1/3)

A new post, as a synthesis of the current series about analyzing PL/SQL code with SonarQube. How to (quickly) evaluate the quality of an application?

Enjoy!