Skip to content

Commit 4e552d2

Browse files
AlexPD93AlexPD93
authoredJun 13, 2024
Initial commit
0 parents  commit 4e552d2

6 files changed

+134
-0
lines changed
 

‎In-House-Project.md

+22
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
# In-House Project
2+
## Guidance
3+
Answer the following questions considering the learning outcomes for this project ([Design Sprint](https://learn.foundersandcoders.com/course/syllabus/developer/projects/in-house-design/learning-outcomes/), [Build Sprint 1](https://learn.foundersandcoders.com/course/syllabus/developer/projects/in-house-build-1/schedule/), [Build Sprint 2](https://learn.foundersandcoders.com/course/syllabus/developer/projects/in-house-build-2/schedule/)) and the different [project roles](https://learn.foundersandcoders.com/course/handbook/project-team/). Make sure to record evidence of your processes. You can use code snippets, screenshots or any other material to support your answers.
4+
5+
Do not fill in the feedback section. The Founders and Coders team will update this with feedback on your progress.
6+
7+
## Assessment
8+
### 1. Explain your role in this project.
9+
> [your answer here]
10+
11+
### 2. Show evidence of a learning outcome you have achieved during this project.
12+
> **[Learning outcome...]**
13+
> [your evidence here]
14+
15+
### 3. Show an example of a learning outcome you have struggled with and/or would like to re-visit.
16+
> **[Learning outcome...]**
17+
> [your evidence here]
18+
19+
## Feedback
20+
> [**Course Facilitator name**]
21+
> [*What went well*]
22+
> [*Even better if*]

‎README.md

+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# Progress Log
2+
3+
## The purpose of the Progress Log
4+
Throughout your time on the 12 week training block, all apprentices are required to keep a Progress Log as part of the programme.
5+
The purpose of the progress log is to enable apprentices to reflect on their learning week by week, identify strengths and areas for development, and to receive feedback on their progress from the Course Facilitators in order to improve.
6+
7+
This progress log must be **updated every Friday** as a reflection activity on the previous week's learning outcomes and **ready for review by Monday morning**.
8+
9+
## Using this template
10+
Follow these steps to create your own Progress Log:
11+
- Click 'Use this template' and select 'Create a new repository'
12+
- Rename the new repository following this convention: **_your-name_--progress-log**
13+
14+
Every week, update the file linked for that week with your reflections and examples of your learnings.
15+
On the following Monday, the Founders and Coders team will review your update and record feedback.
16+
17+
## Weekly Learnings
18+
- [Week 1-3](/Week_1-3.md)
19+
- [Week 4-6](/Week_4-6.md)
20+
- [Week 7-9](/Week_7-9.md)
21+
- [Week 10-12. Tech for Better Project](/Tech-For-Better-Project.md)

‎Tech-For-Better-Project.md

+22
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
# Tech-For-Better Project
2+
## Guidance
3+
Answer the following questions considering the learning outcomes for this project ([Design Sprint](https://learn.foundersandcoders.com/course/syllabus/developer/projects/tfb-design/learning-outcomes/), [Build Sprint 1](https://learn.foundersandcoders.com/course/syllabus/developer/projects/tfb-build-1/learning-outcomes/), [Build Sprint 2](https://learn.foundersandcoders.com/course/syllabus/developer/projects/tfb-build-2/learning-outcomes/)) and the different [project roles](https://learn.foundersandcoders.com/course/handbook/project-team/). Make sure to record evidence of your processes. You can use code snippets, screenshots or any other material to support your answers.
4+
5+
Do not fill in the feedback section. The Founders and Coders team will update this with feedback on your progress.
6+
7+
## Assessment
8+
### 1. Explain your role in this project.
9+
> [your answer here]
10+
11+
### 2. Show evidence of a learning outcome you have achieved during this project.
12+
> **[Learning outcome...]**
13+
> [your evidence here]
14+
15+
### 3. Show an example of a learning outcome you have struggled with and/or would like to re-visit.
16+
> **[Learning outcome...]**
17+
> [your evidence here]
18+
19+
## Feedback
20+
> [**Course Facilitator name**]
21+
> [*What went well*]
22+
> [*Even better if*]

‎Week_1-3.md

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
## Guidance
2+
Answer the following questions considering the learning outcomes for
3+
- [Week 1](https://learn.foundersandcoders.com/course/syllabus/developer/project-1-server/learning-outcomes/)
4+
- [Week 2](https://learn.foundersandcoders.com/course/syllabus/developer/project-1-frontend/learning-outcomes/)
5+
- [Week 3](https://learn.foundersandcoders.com/course/syllabus/developer/project-1-test-deploy/learning-outcomes/)
6+
7+
Make sure to record evidence of your processes. You can use code snippets, screenshots or any other material to support your answers.
8+
9+
Do not fill in the feedback section. The Founders and Coders team will update this with feedback on your progress.
10+
11+
## Assessment
12+
### 1. Show evidence of some of the learning outcomes you have achieved this week.
13+
> **[Learning outcomes...]**
14+
> [your evidence here]
15+
16+
### 2. Show an example of some of the learning outcomes you have struggled with and/or would like to re-visit.
17+
> [**Learning outcome...**]
18+
> [your evidence here]
19+
20+
## Feedback (For CF's)
21+
> [**Course Facilitator name**]
22+
> [*What went well*]
23+
> [*Even better if*]

‎Week_4-6.md

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
## Guidance
2+
Answer the following questions considering the learning outcomes for
3+
- [Week 4](https://learn.foundersandcoders.com/course/syllabus/developer/project-2-week-1/learning-outcomes/)
4+
- [Week 5](https://learn.foundersandcoders.com/course/syllabus/developer/project-2-week-2/schedule/)
5+
- [Week 6](https://learn.foundersandcoders.com/course/syllabus/developer/project-2-week-3/learning-outcomes/)
6+
7+
Make sure to record evidence of your processes. You can use code snippets, screenshots or any other material to support your answers.
8+
9+
Do not fill in the feedback section. The Founders and Coders team will update this with feedback on your progress.
10+
11+
## Assessment
12+
### 1. Show evidence of some of the learning outcomes you have achieved this week.
13+
> **[Learning outcomes...]**
14+
> [your evidence here]
15+
16+
### 2. Show an example of some of the learning outcomes you have struggled with and/or would like to re-visit.
17+
> [**Learning outcome...**]
18+
> [your evidence here]
19+
20+
## Feedback (For CF's)
21+
> [**Course Facilitator name**]
22+
> [*What went well*]
23+
> [*Even better if*]

‎Week_7-9.md

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
## Guidance
2+
Answer the following questions considering the learning outcomes for
3+
- [Week 7](https://learn.foundersandcoders.com/course/syllabus/developer/project-1-server/learning-outcomes/)
4+
- [Week 8](https://learn.foundersandcoders.com/course/syllabus/developer/project-1-frontend/learning-outcomes/)
5+
- [Week 9](https://learn.foundersandcoders.com/course/syllabus/developer/project-1-test-deploy/learning-outcomes/)
6+
7+
Make sure to record evidence of your processes. You can use code snippets, screenshots or any other material to support your answers.
8+
9+
Do not fill in the feedback section. The Founders and Coders team will update this with feedback on your progress.
10+
11+
## Assessment
12+
### 1. Show evidence of some of the learning outcomes you have achieved this week.
13+
> **[Learning outcomes...]**
14+
> [your evidence here]
15+
16+
### 2. Show an example of some of the learning outcomes you have struggled with and/or would like to re-visit.
17+
> [**Learning outcome...**]
18+
> [your evidence here]
19+
20+
## Feedback (For CF's)
21+
> [**Course Facilitator name**]
22+
> [*What went well*]
23+
> [*Even better if*]

0 commit comments

Comments
 (0)
Please sign in to comment.