In the improvement section of the curriculum, there are plenty of phrases that could lead to the impression that this course is all about legacy code refactoring.
Examples:
In LG 5-2: Know and being able to apply typical technology/programming language-specific refactorings (semantics preserving simplification measures in source code). Training should conduct exercises if required.
In LG 5-3: now and being able to autonomously apply automated tests ...
This could lead to different expectations regarding attendees as well as different training approaches of trainers. To fix this, we need to sharpen what should be talked about in IMPROVE and what not. E.g., topics like using IDEs to refactor code are other training courses for software developers.
In the improvement section of the curriculum, there are plenty of phrases that could lead to the impression that this course is all about legacy code refactoring.
Examples:
This could lead to different expectations regarding attendees as well as different training approaches of trainers. To fix this, we need to sharpen what should be talked about in IMPROVE and what not. E.g., topics like using IDEs to refactor code are other training courses for software developers.