Raise code quality
Identify friction points in code and practices, then push concrete improvements rather than a theoretical audit with no follow-up.
Case study
Raising code quality on a business ERP
Working on the code quality of a central business system, and bringing an outside technical perspective to the team’s debates.
The engagement focused on the ERP of the Foncia group, now Emeria, Europe’s leading real-estate services provider: a central business system where technical choices must remain understandable to teams and compatible with operational constraints.
What we worked on
Contribute to technical debates
Bring an outside perspective to discussions of architecture, debt and remediation priorities (the calls remained the team’s to make).
Make the reasoning explicit
Lay out the arguments behind each option so the team could challenge them, decide for itself and maintain the result after the engagement.
Account for the business domain
Connect technical quality to actual ERP usage: reliability, evolvability, maintenance and the ability to absorb field-team needs.
What this engagement shows
An outside contributor is not measured by their opinion, but by what the team can take over: healthier code, and arguments it can reuse without us.
Topics and technologies
A similar context?
We can frame the engagement, identify technical risks and leave your teams able to take ownership.
Talk to us