Answer the following questions considering the learning outcomes for
Make sure to record evidence of your processes. You can use code snippets, screenshots or any other material to support your answers.
Do not fill in the feedback section. The Founders and Coders team will update this with feedback on your progress.
This week I improved greatly my PR Requests, commits, documentation, code readability. I have also continued with Exectute Program. I am currently doing 2 courses: SQL and Everyday TypeScript.
Will and Jack set the back-end and front-end server and when they did the initial setting, they also automated or implemented a standard way of doing PR Requests, commit messages, updating README.md file and folder structure. This led to an amazingly organised use og Git, which makes life so much easier for me to check my colleagues code, finding all the answers to understand what they have done without having to ask them and loose time.
- Our commits guidelines:
- My commits:
- My PR Request structure following the PR guidelines we implemented:
- Our Database structure:
2. Show an example of some of the learning outcomes you have struggled with and/or would like to re-visit.
Making our Zubi project mobile first and responsive. It can be time consuming at the beginning of the project, but it is an absolute blessing later in the project because now our website is looking great!
[Course Facilitator name]
Alexander
[What went well]
I love how you all improved on your PR. This good practices will make your life much easier when you start working in a company.