Un projet en perdition
I was hired for KRAO, a project that had accumulated months of delays. Several developers had worked on it successively, and the code had become unmanageable.
My mission could be summed up in one sentence: get it back on track. I was working on it alone, supported by a project lead who knew the project's history and answered my questions.
The project was months behind schedule, and the code was no longer sustainable. The door system was buggy everywhere, and even the developer who had written it could no longer fix one error without causing another elsewhere.
Take over the project, make it maintainable, and bring it through to deployment at the Kouvola training center.
Software engineer, working alone on taking over the project, supported by a subject-matter expert familiar with its history.
The existing system was inefficient, unstable, and unmaintainable. Complete rewrite, in agreement with my management, based on SOLID, DRY, and KISS principles.
A large part of the interface, using an MVVM architecture connected to the Unity engine.
Real-time voice communication between the learner in the simulation cab and their instructors in the control cab.
- Complete rewrite of the door system rather than yet another patch: the existing system could no longer be fixed without breaking something else.
- SOLID, DRY and KISS applied during the overhaul to make the code maintainable by someone other than its author.
- Communications restricted to the training centre's network: no calls to the outside.