Ground rules

In order to guarantee a smooth progress we've set up some ground rules. This isn't as serious as it sounds. The teachers won't act like referees. We did find out though that abiding by these practices will be very helpful.

• Always start your branch names with feature/. It's derived from the "Git flow" pattern; a way of working for Git repositories. It will be useful to identify what's on a branch and to target certain automation processes.
• Never copy code from other trainees or let other trainees copy your code. Be like a coach and assist them step by step in resolving their issue.
• Programming problems are like puzzles you can solve effectively by working step by step. Especially when a problem seems very complex, take a notebook and a pen to break down the problem into smaller parts and write them down.
• Always handle the feedback that has been provided in a code review. This can either be to process the input, ask for elaboration on the feedback, or explain why you made another decision.
• Never take review feedback as truth. The reviewer might be mistaken, misinformed or not aware of certain limitations. Assess whether the feedback makes sense before you change your code. Either way make sure the reviewer is on board with your action.
• Always review the work of other trainees.
• Always update the project board if the status of a task changes.
• As you are still learning to become a competent programmer, we discourage you asking ChatGPT for help and copying its answer without knowing what you are doing. This way you don't learn, and you might add erroneous code to your application without being aware of it. Neither do we encourage to make use of GitHub Copilot.
• Don't forget to enjoy the learning process. Programming can be difficult and dense at times, but your learning curve will be steep so you will reap the rewards very soon!