Skip to content

Latest commit

 

History

History
41 lines (21 loc) · 2.12 KB

Week_01.md

File metadata and controls

41 lines (21 loc) · 2.12 KB

Guidance

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.

Assessment

1. Show evidence of some of the learning outcomes you have achieved this week.

Learned a lot about the Git workflow

Understood the importance of pulling into main before pushing to the remote repo to make sure that any merge conflicts are happening on your local machine.

2. Show an example of some of the learning outcomes you have struggled with and/or would like to re-visit.

This week was not too strenuous in terms of learning outcomes.

A lot of the curriculum was frontend stuff which is where the majority of my experience lies. I would like to revisit the Asynchronous JS Execute Program module as, while I have previously learned Promises, I moved onto Async/Await and all my knowledge of Promises has gone. It has not been easy relearning Promises!!!

Going Forward, I would also like to work on different features in different branches

This is something that I neglected to do in this project and, while it didn't lead to catastrophe, it will someday!!!

Feedback (For CF's)

[Course Facilitator name]

Alexander

[What went well]

Creating good habits on git workflow may be the most important outcome for this week, and looks like you got it. It also looks like you have good basics regarding async code. No worries if you feel like you still don't master promises. Whenever you start working on real projects you will find them and just understanding them will be enough. If you create your own code you still can choose whatever feels better for you.

[Even better if]

You could add a few one-liners for specific topics, like the technical struggles you had in your project. A short description with a code snippet is very effective.