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
Copy file name to clipboardExpand all lines: Week1/MAKEME.md
+11-13Lines changed: 11 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -11,36 +11,34 @@ Topics discussed in class this week:
11
11
12
12
_Deadline Monday_
13
13
14
-
All share a video or a resource (this can be a drawing, article or a pod cast) that was helpful for you the last few weeks with learning JavaScript. Please share this in the channel of your class in Slack. Also write as small note about what the resource i about and why you think it's so helpful (you can share more than one if you like).
14
+
All share a video or a resource (this can be a drawing, an article or a podcast) that was helpful for you the last few weeks with learning JavaScript. Please share this in the channel of your class in Slack. Also write as small note about what the resource is about and why you think it's so helpful (you can share more than one if you like).
15
15
16
16
## Step 2: Feedback
17
17
18
18
_Deadline Monday_
19
19
20
-
Give one of your fellow students in Github feedback about their homework of the previous week: create an issue in their repo, telling them what they did great and what they can improve.
20
+
Give one of your fellow students feedback in Github about their homework of the previous week: Create an issue in their repo, telling them what they did great and what they can improve.
21
21
22
-
Step3
23
22
24
23
## Step 3: Git homework
25
24
26
25
_Deadline Wednesday_
27
26
28
27
Git homework for this week:
29
28
30
-
Pair up with another student in your class. The homework requires two people to work together. Let us call them admin and user.
29
+
Pair up with another student in your class. The homework requires two people to work together. Let's call them admin and user.
31
30
32
31
1. admin creates a new repository on github called “animals” (without quotes).
33
-
2. admin adds a file called “zoo.txt” with some animal generally found in a zoo.
34
-
3. admin commits and pushes his changes (in master branch)
35
-
4. admin adds user as a collaborator (find out how to add a collaborator to a git repository)
36
-
5. user clones a repository from admin (find out how to clone a repository. Note that `git init` is not required when you clone a repository)
37
-
6. user makes a new branch called user-dev
32
+
2. admin adds a file called “zoo.txt” with some animals generally found in a zoo.
33
+
3. admin commits and pushes his changes (in master branch).
34
+
4. admin adds user as a collaborator (find out how to add a collaborator to a git repository).
35
+
5. user clones the repository from admin (find out how to clone a repository. Note that `git init` is not required when you clone a repository).
36
+
6. user makes a new branch called user-dev.
38
37
7. user adds another file called “pets.txt” with some animals generally found in a home.
39
-
8. user commits and pushes his branch to remote
40
-
9. admin pulls the branch crated by user (find out how to pull changes from the repository)
41
-
10. admin submits the link to his github repository (named animal), where unmesh should be able to see the collaborator’s (i.e. user’s) branch along with his commits.
38
+
8. user commits and pushes his branch to remote.
39
+
9. admin pulls the branch crated by user (find out how to pull changes from a repository).
40
+
10. admin submits the link to his github repository (named "animals"), where Unmesh should be able to see the collaborator’s (i.e. user’s) branch along with his commits.
42
41
43
42
Note:
44
43
45
44
The *user* is *not supposed to fork* the admin’s repository. *admin* is supposed to add user as a collaborator and *user* should just *clone* the repository (i.e. *user* will only have the local copy of the repository). Only *admin* will have the *github* server copy of the repository. Of course, admin will have its local copy of the repository too.
Copy file name to clipboardExpand all lines: Week2/MAKEME.md
+41-37Lines changed: 41 additions & 37 deletions
Original file line number
Diff line number
Diff line change
@@ -13,12 +13,12 @@ Topics discussed in class this week:
13
13
## Before you start with the homework:
14
14
15
15
1. Review the [Git course material](https://github.com/HackYourFuture/Git) of last week.
16
-
2. Watch: [What is programming](https://www.khanacademy.org/computing/computer-programming/programming/intro-to-programming/v/programming-intro) Just watch the 2 min video, you do not have to do the entire JavaScript course (It could be useful later on though).
17
-
3. Please watch the following parts of the course, [Programming Foundations Fundamentals](https://www.lynda.com/Programming-Foundations-tutorials/Welcome/83603/90426-4.html) on Lynda.com (if you don't have access to Lynda yet ask Gijs):
18
-
0\. Introduction
19
-
1\. Programming Basics
20
-
2\. Core Programming Syntax
21
-
3\. Variables and Data Types
16
+
2. Watch: [What is programming](https://www.khanacademy.org/computing/computer-programming/programming/intro-to-programming/v/programming-intro), just watch the 2 min video, you do not have to do the entire JavaScript course (It could be useful later on though).
17
+
3. Please watch the following parts of the course, [Programming Foundations Fundamentals](https://www.lynda.com/Programming-Foundations-tutorials/Welcome/83603/90426-4.html) on Lynda.com (if you don't have access to Lynda yet ask Gijs):
18
+
0\. Introduction
19
+
1\. Programming Basics
20
+
2\. Core Programming Syntax
21
+
3\. Variables and Data Types
22
22
23
23
24
24
## Step 2: Feedback
@@ -31,11 +31,12 @@ Provide feedback on the Git assignments (week 1) of one of your fellow students.
31
31
32
32
_Deadline Thursday_
33
33
34
-
> For all the following exercises create a new .js file. Try to find a proper name for each file or make a small comment about what it does inside for future reference.
34
+
> For all the following exercises create a new `.js` file. Try to find a proper name for each file or make a small comment about what it does inside for future reference.
35
35
36
-
1\. Write a `console.log` statement saying "Hello World!" for each language that you know.
36
+
1\. Write a `console.log` statement saying "Hello World!" for each language that you know.
37
37
38
38
For example:
39
+
39
40
```
40
41
Halo, dunia! // Indonesian
41
42
Ciao, mondo! // Italian
@@ -44,25 +45,27 @@ Hola, mundo! // Spanish
44
45
45
46
2\. Consider the following code:
46
47
47
-
```
48
+
```js
48
49
console.log('I'm awesome');
49
50
```
50
51
51
52
Copy the code in your `.js` file and run it. You will see that you will get a SyntaxError. Find a solution for this error. Hint: read the error message carefully, it also gives an indication of where the problem is.
52
53
53
-
3\. Declare a variable `x` and initialize it with an integer, using these exact steps:
54
+
3\. Declare a variable `x` and initialize it with an integer, using these exact steps:
54
55
3\.1 First, _declare_ your variable `x` (do not initialize it yet).
55
-
3\.2 Add a console.log statement that explains that explains in words what _you think_ the value of `x` is, like in this example:
56
+
3\.2 Add a `console.log` statement that explains in words what _you think_ the value of `x` is, like in this example:
57
+
56
58
```js
57
59
// TODO -> here you initialize your variable
58
60
console.log('the value of my variable x will be: whateverYouThinkItWillLog');
59
61
```
60
-
3\.3 Add a console.log statement that logs the value of `x`.
62
+
63
+
3\.3 Add a `console.log` statement that logs the value of `x`.
61
64
3\.4 Now _initialize_ your variable `x` with an integer.
62
-
3\.5 Next, add a console.log statement that explains what _you think_ the value of `x` is.
63
-
3\.6 Add a console.log statement that logs the value of `x`.
65
+
3\.5 Next, add a `console.log` statement that explains what _you think_ the value of `x` is.
66
+
3\.6 Add a `console.log` statement that logs the value of `x`.
64
67
Steps to be taken:
65
-
68
+
66
69
```js
67
70
// TODO -> here you declare your variable
68
71
console.log('the value of x will be: whateverYouThinkItWillLog');
@@ -73,11 +76,12 @@ Copy the code in your `.js` file and run it. You will see that you will get a Sy
73
76
```
74
77
75
78
4\. Declare a variable `y` and assign a string to it.
76
-
4\.1 Write a console.log statement in which you explain in words what _you think_ the value of the string is.
77
-
4\.2 Now console.log the variable `y`.
79
+
4\.1 Write a `console.log` statement in which you explain in words what _you think_ the value of the string is.
80
+
4\.2 Now `console.log` the variable `y`.
78
81
4\.3 Now assign a new string to the variable `y`.
79
-
4\.4 Just like you did before write a console.log statement that explains in words what you think will be logged to the console.
82
+
4\.4 Just like what you did before write a `console.log` statement that explains in words what you think will be logged to the console.
80
83
4\.5 Now console.log `y` again.
84
+
81
85
```js
82
86
// TODO -> here you declare AND assign your string
83
87
console.log('the value of my string will be: whateverYouThinkItWillLog');
@@ -89,38 +93,38 @@ Copy the code in your `.js` file and run it. You will see that you will get a Sy
89
93
90
94
5\. How do you round the number 7.25, to the nearest integer (i.e., whole number)?
91
95
5\.1 Declare a variable `z` and assign the number 7.25 to it.
92
-
5\.2 Console.log `z`.
93
-
5\.3 Declare another variable `a` that has the value of z but rounded to the nearest integer.
94
-
5\.4 Console.log `a`.
96
+
5\.2 `console.log` `z`.
97
+
5\.3 Declare another variable `a` that has the value of `z` but rounded to the nearest integer.
98
+
5\.4 `console.log` `a`.
95
99
5\.5 So now we have `z` and `a` find a way to compare the two values and store the highest of the two in a new variable.
96
-
5\.6 Console.log the highest value.
100
+
5\.6 `console.log` the highest value.
97
101
98
-
6\.*Arrays!*
99
-
6\.1 Declare an empty array. Make sure that the name you choose indicates 'plurality', because an array is capable of containing more than one element. (See [Naming conventions](../fundamentals/naming_conventions.md).)
100
-
6\.2 Write a console.log statement that explains in words what you think the value of the array is.
101
-
6\.3 Console.log your array.
102
-
6\.4 Create an array that has your favorite animals inside (see if you can find a good name that exactly describes what this variable will hold).
102
+
6\. *Arrays*
103
+
6\.1 Declare an empty array. Make sure that the name you choose indicates 'plurality', because an array is capable of containing more than one element. (See [Naming conventions](../fundamentals/naming_conventions.md)).
104
+
6\.2 Write a `console.log` statement that explains in words what you think the value of the array is.
105
+
6\.3 `console.log` your array.
106
+
6\.4 Create an array that has your favorite animals inside (see if you can find a good name that exactly describes what this variable will hold).
103
107
6\.5 Log your array.
104
108
6\.6 Add a statement that adds Daan's favorite animal ('baby pig') to the *existing array*.
105
109
6\.7 Log your newarray!
106
110
107
111
7\. *More strings*
108
-
7\.1 Let's consider the following string: `let myString = "this is a test"`.
109
-
7\.2 Add the string to your file and console.log it.
110
-
7\.3 Find a way to get the length of `myString`.
111
-
7\.4 Console.log the length of `myString`.
112
+
Let's consider the following string: `let myString = "this is a test"`.
113
+
7\.1 Add the string to your file and console.log it.
114
+
7\.2 Find a way to get the length of `myString`.
115
+
7\.3 `console.log` the length of `myString`.
112
116
113
117
8\. Write a program that checks the types of two variables and prints out `SAME TYPE` if they are the same type.
114
118
8\.1 First declare at least four variables and assign them different data types.
115
-
8\.2 For each variable write a `console.log` statement that logs the value
116
-
```js
119
+
8\.2 For each variable write a `console.log` statement that logs the value
120
+
```js
117
121
let foo = 3;
118
122
console.log('The value of my variable foo is:' + foo);
119
123
```
120
124
121
-
(Curious to know what a `foo` is? Check [this article](https://en.wikipedia.org/wiki/Metasyntactic_variable) on WikiPedia.)
125
+
(Curious to know what a `foo` is? Check [this article](https://en.wikipedia.org/wiki/Metasyntactic_variable) on Wikipedia.)
122
126
123
-
8\.3 Now write a console.log statement wherein you first explain in words what you think the _type_ of your variables is.
127
+
8\.3 Now write a `console.log` statement wherein you first explain in words what you think the _type_ of your variables is.
124
128
8\.4 Now use `typeof` to log the actual _type_ of your variables.
125
129
8\.5 Now compare the types of your different variables with one another.
126
130
8\.6 Make sure to also show a message when the variables you are comparing are not the same type.
@@ -143,7 +147,7 @@ if (...) {
143
147
10\. Write a program to answer the following questions:
144
148
10\.1 Can you store multiple types in an array? Numbers and strings? Make an example that illustrates your answer.
145
149
10\.2 Can you compare infinities? (Not in Eyad's world) - does 6/0 === 10/0? How can you test this?
146
-
10\.3 Add console.log statements to the above program's in which you show that you understand the concepts (just like you've done in the above assignments).
150
+
10\.3 Add `console.log` statements to the above program in which you show that you understand the concepts (just like you've done in the above assignments).
0 commit comments