Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set a clearer scope of the level of IMPROVE #45

Closed
feststelltaste opened this issue Jul 11, 2024 · 0 comments · Fixed by #49
Closed

Set a clearer scope of the level of IMPROVE #45

feststelltaste opened this issue Jul 11, 2024 · 0 comments · Fixed by #49
Assignees
Labels

Comments

@feststelltaste
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging a pull request may close this issue.

1 participant