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
{{ message }}
This repository was archived by the owner on Aug 17, 2024. It is now read-only.
Code review is a valuable skill for a developer, and is a good way to practice talking about code with confidence. Let's level up our code review now.
35
159
36
160
1. Review Google's [engineering guide on code review](https://google.github.io/eng-practices/review/reviewer/comments.html).
37
161
2. In your Buddy group, code review each of your colleague's nominated pull reqs.
38
162
3. Stretch: Try [suggesting line changes](https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request#applying-suggested-changes), and accepting them yourself:
@@ -47,21 +171,21 @@ Find the collection for JS-1 Week 3 on the CodeYourFuture account: https://www.c
47
171
48
172
Have you found the [Troubleshooting Guide](https://docs.codewars.com/training/troubleshooting/) yet? :D
49
173
50
-
## 7) Learn About the Terminal part 2 (4 hours)
174
+
## 5) Learn About the Terminal part 2 (4 hours)
51
175
52
176
Most developers spend a lot of time using something called the terminal. This week, you are going to follow a course to learn about the terminal - it has [its own homework page here](/git/terminal/homework) for you to work from.
53
177
54
178
You should have started this course last week. Complete it now.
55
179
56
-
## 8) (Stretch) Extra JavaScript Challenges
180
+
## 6) (Stretch) Extra JavaScript Challenges
57
181
58
182
Have some extra time before our next class? Fill it with these harder challenges to help you stretch your abilities.
59
183
60
184
**Alert:** Some of these challenges might include concepts that we haven't taught you yet. You should expect to frequently encounter concepts you haven't been taught in class yet or at all. Learning how to tackle this is a crucial skill we are supporting you to develop. How will you handle this? Will you create a study group? Find a mentor? Ask for a session in class? It's your professional development, so take control of it.
Imagine yourself in one of the following scenarios. How would you prepare to give constructive feedback in that situation?
67
191
@@ -74,10 +198,10 @@ Scenarios:
74
198
- Your colleague keeps interrupting you and others in meetings
75
199
- Your flatmate left dirty cups in the sink for several days
76
200
77
-
## 10) Working with your team (PD - 2 hr)
201
+
## 8) Working with your team (PD - 2 hr)
78
202
79
203
Feedback from colleagues gives you insight into your career progress. Every week you will be requesting feedback from two people. This will give you insight into your progress on this course.
80
204
81
205
This week, invite a classmate for a call. Choose someone you have worked with in a small group. Invite your PD or Education Buddy too. Exchange feedback. Try to be helpful, candid, and kind.
82
206
83
-
Write a 250 word essay reflecting on your strengths and development areas. Use the feedback to help you write this essay.
207
+
Write a 250 word essay reflecting on your strengths and development areas. Use the feedback to help you write this essay.
Copy file name to clipboardExpand all lines: docs/js-core-1/week-3/mentors.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,33 @@ We highly recommend joining the relevant Slack Channel for this module. In this
16
16
17
17
For general Syllabus feedback and help you can post in [cyf-syllabus](https://codeyourfuture.slack.com/archives/C012UUW69S8)
18
18
19
+
## Flipped classroom recap/Q&A
20
+
21
+
The flipped classroom practice should have trainees
22
+
23
+
- Get a basic understanding of truthiness and falsiness (see notes below)
24
+
- In particular, using an `if (argumentToFunction)` for functions with optional arguments
25
+
-`let foo = val || "default value"` and `if (val && val.foo === 3)` are not yet covered
26
+
- Write and run programs using basic array functionality
27
+
- initialise an array: `const names = ["Biruk", "Ali", "Mitch"];`
28
+
- access a zero-indexed element: `let ali = names[1];`
29
+
- modify a zero-indexed element: `names[2] = "Jyoti"`
30
+
- get the length of an array: `let countNames = names.length`
31
+
- add elements to an array: `names.push("Zsolt")`
32
+
- Iterate through an array using `for (const name of names) {console.log(name);}`
33
+
- Iterate through an array using `for (let i=0; i<names.length; i++) {console.log(i, names[i])}`
34
+
- it is not important at this stage for all trainees to understand this (it's included only for completeness as trainees will find these loops through stackoverflow/google)
35
+
- equivalence between c-style for and while loop is not yet clarified
36
+
- Note: array methods are not covered, particularly 2nd order functions: `.filter()`, `.map()`, `.forEach()`
37
+
38
+
Some questions/prompts that may be useful
39
+
40
+
- What does this program do? (show programs of varying degrees of complexity using arrays)
41
+
- What does this expression evaluate to, using array expressions?
42
+
- What kinds of data types have we seen so far? (without getting too technical, "string", "number", "boolean", "undefined"). What values are falsy/truthy?
43
+
- What are some ways to iterate over an array? Why would we use one over the other?
44
+
- Discuss solutions to practice exercises
45
+
19
46
## Notes on truthy, falsy, null, and undefined
20
47
21
48
This session is only to establish some initial habits of thought, especially around debugging. This is such a tricky idea to grasp and so helpful to understand, so talk a little bit about different errors produced by these states.
0 commit comments