Skip to the content.

% How to reduce bloatware technical debt?

Old software project

Software started in the early years 2000 share similar characteristics:

Advices

This document provides some advices. Depending on the project specificities and on the team culture, some advices are relevant, some others can be skipped.

This change is part of the continuous improvement. Therefore, team members are encouraged to propose many more suggestions over the months.

Risk Management

Therefore, before any change, implement combined “safety belt and shoulder harness” (ceinture et bretelles).

As these verifications have to be reproducible, script the building and comparison processes.

Artifact Repository

Provide recent tools

The team decides the list of tools. Example:

Rewrite outdated build scripts

CMake

Source code Urbanization

Improve documentation

Test suite

Create or complete:

Decide the tests to add according to code-coverage and usage model.

Continuous Testing

Several Continuous Integration passes

Tricks

Remove unnecessary code

More warnings

Performance

Continuous code cleaning & refactoring

Continuous Delivery

Copyright

Libre software