You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will involve writing a medium-quality codebase our trainees can work in to do things like: Orient themselves, find bugs, fix bugs, add new features. We don't want to give them perfect code, or terrible code, but a realistic mix. We will need to provide specific tasks for them to do in this codebase.
We will also want to curate or create content giving techniques and advice on how to approach existing code.
We have the following draft learning objectives (which we can change if we need):
Understanding legacy code
Explain the functionality offered by existing code
Sketch the flow of a request through existing code
Debugging legacy code
Identify the code responsible for a bug reported against existing code
Identify the root cause of a bug reported against existing code
Fixing legacy code
Identify and implement a fix for a bug in existing code
We need to create the SDC Legacy Code module.
This will involve writing a medium-quality codebase our trainees can work in to do things like: Orient themselves, find bugs, fix bugs, add new features. We don't want to give them perfect code, or terrible code, but a realistic mix. We will need to provide specific tasks for them to do in this codebase.
We will also want to curate or create content giving techniques and advice on how to approach existing code.
We have the following draft learning objectives (which we can change if we need):
Understanding legacy code
Debugging legacy code
Fixing legacy code
Extending legacy code
We also have some experience in this from the CYF+ course "buggy app" project - talk to @illicitonion to get some lessons learned from watching people attempt this project.
The text was updated successfully, but these errors were encountered: