Legacy Code Workshop
I've chosen a low-level hardware-related module of one of my personal projects: there was a lot of dependencies to microprocessor's .h files to be broken before starting to write the tests for the modules. For me it was a good example because in embedded environment this dependencies are really strong.
How to improve:
In our workshop we've started with a legacy code chosen from DALI libraries provided by a collegue of us, but after some tries we switched to another one (mine) that could have been more interesting. Unfortunately, because of the workspace compilation troubles of a lot of us there wasn't a common line and a common example that everyone followed and each one went forward with his personal example ...that indeed was a also good thing because eachone was forced to face real problems with his keyboard in hand...
Actually I don't know what could have been better:
- giving the chance to each-one to face specific problems in real personal legacy code (with the help of the teacher shared among all the students)
- all the students following one or two real examples of pre-chosen real legacy code with specific tecniques applyed
For sure we've lost a lot of time with the workspace problems...