fixed some homework mistakes

mkruijt · mkruijt · commit 9fe7d7262a75 · 2017-11-29T14:09:37.000+01:00
diff --git a/Week3/MAKEME.md b/Week3/MAKEME.md
@@ -101,6 +101,12 @@ _Deadline Sunday morning_
 
 And just for fun ... https://www.freecodecamp.com/challenges/sum-all-numbers-in-a-range
 
+## Step 6: Read before next lecture
+
+_Deadline Sunday morning_
+
+Go trough the reading material in the [README.md](/Week3/README.md) to prepare for your next class 
+
 ### :boom: Bonus homework :boom:
 the Bonus homework for this week (for those of you want an extra challenge) do the following:
 
diff --git a/Week6/MAKEME.md b/Week6/MAKEME.md
@@ -103,38 +103,7 @@ console.log(y);
 If you are confused please run the code and then consult the Google for "javaScript pass by value pass by reference"
 
 
-<!-- Write assignment with more fun API -->
-
-### Step 4: Some more JavaScript
-
-_Deadline Saturday_
-
-Make a website that fetches (= to get) data asynchronously.
-
-1) Create a new website with external js file
-
-2) Add a button (e.g. 'click me') that when clicked `console.logs` 'you clicked me!'
-
-3) Create a function that fetches from [The Github API](https://developer.github.com/v3/). For example from [this page] (https://api.github.com/orgs/HackYourFuture/repos) (the one we used last week). For help on this check this [SO post](https://stackoverflow.com/questions/247483/http-get-request-in-javascript)
-
-4) Display the data that you get from the Github API on your web page.
-
-5) Now link the two together: When you click the button -> get the data from the Github API and display it on your website
-
-6) Make all the repositories link their own page in Github. Use the value of the key: `name` to make this work (hint: Github urls always look like this https://api.github.com/repos/HackYourFuture/[repositoryName] where [repositoryName] would be replaced by the actual `name` of the repository, for example `CommandLine`). Make sure the link opens in a new tab.
-
-7) BONUS: if you look at this:
-
-```js
-https://api.github.com/repos/HackYourFuture/CommandLine
-```
-
-You can see `CommandLine` in the URL. These are called "query parameters" and let us specify in detail what we want from the API. Play around with this. For example you can make two buttons that either get data for a specific repository, JavaScript or Node.js. Or go even more crazy and make users type in a search box 'JavaScript' and then send that to the API by changing the repository.
-
-__Bonus__: Write a function takes this array `['a', 'b', 'c', 'd', 'a', 'e', 'f', 'c']` and returns an array which only has unique values in it (so it removes the duplicate ones). Make it a 'smart' algorithm that could do it for every array (only strings/number). Try to make it as fast as possible!
-
-
-### Step 5: Read before next lecture
+### Step 4: Read before next lecture
 
 _Deadline Sunday morning_
 
diff --git a/Week7/MAKEME.md b/Week7/MAKEME.md
@@ -22,64 +22,37 @@ Give feedback on the SPA (Github API) and git branching homework of one of you f
 
 - Fix the issues from the last week and make sure you explain how you fixed the issue in a comment (or commit message)
 
+<!-- Write assignment with more fun API -->
 
-### Step 4: SPA :sweat_drops:
-You are going to write a SPA (Single Page Application) that uses the [Github API](https://developer.github.com/guides/getting-started/). Make sure that your app uses a logical pattern just like [this codepen](http://codepen.io/Razpudding/pen/MmVpeW).
+### Step 4: Some more JavaScript
 
-Just like last week:
+_Deadline Saturday_
 
 Make a website that fetches (= to get) data asynchronously.
 
 1) Create a new website with external js file
 
 2) Add a button (e.g. 'click me') that when clicked `console.logs` 'you clicked me!'
 
-3) Create a function that fetches from [The Github API](https://developer.github.com/v3/). For example from [this page] (https://api.github.com/orgs/HackYourFuture/repos). For help on this check this [SO post](https://stackoverflow.com/questions/247483/http-get-request-in-javascript)
+3) Create a function that fetches from [The Github API](https://developer.github.com/v3/). For example from [this page] (https://api.github.com/orgs/HackYourFuture/repos) (the one we used last week). For help on this check this [SO post](https://stackoverflow.com/questions/247483/http-get-request-in-javascript)
 
 4) Display the data that you get from the Github API on your web page.
 
 5) Now link the two together: When you click the button -> get the data from the Github API and display it on your website
 
-Cool we are back where we left of.
+6) Make all the repositories link their own page in Github. Use the value of the key: `name` to make this work (hint: Github urls always look like this https://api.github.com/repos/HackYourFuture/[repositoryName] where [repositoryName] would be replaced by the actual `name` of the repository, for example `CommandLine`). Make sure the link opens in a new tab.
 
-6) Take a look at this:
+7) BONUS: if you look at this:
 
 ```js
 https://api.github.com/repos/HackYourFuture/CommandLine
 ```
 
-7) Make a function which takes a single argument. The function should make an XHR request to `https://api.github.com/repos/HackYourFuture/[SearchTerm]` where the search term will be the argument. This argument will be the input the user has given you, so make sure that when the user clicks the button you call this function with the argument. 
+You can see `CommandLine` in the URL. These are called "query parameters" and let us specify in detail what we want from the API. Play around with this. For example you can make two buttons that either get data for a specific repository, JavaScript or Node.js. Or go even more crazy and make users type in a search box 'JavaScript' and then send that to the API by changing the repository.
 
-8) Make all the repositories link their own page in Github. Use the value of the key: `name` to make this work (hint: Github urls always look like this https://api.github.com/repos/HackYourFuture/[repositoryName] where [repositoryName] would be replaced by the actual `name` of the repository, for example `CommandLine`). Make sure the link opens in a new tab.
+__Bonus__: Write a function takes this array `['a', 'b', 'c', 'd', 'a', 'e', 'f', 'c']` and returns an array which only has unique values in it (so it removes the duplicate ones). Make it a 'smart' algorithm that could do it for every array (only strings/number). Try to make it as fast as possible!
 
-- Make sure you handle user input well. That means you need to think about empty input, and input that doesn't yield any results.
 
-So Github has this really nice documentation :octocat: :
-Check these out for example
-https://developer.github.com/v3/repos/collaborators/
-https://developer.github.com/v3/repos/commits/
-
-9) Extend your page with an input element. This is so the user will be able to type in text.
-
-10) For each repository, show (in the right column) who the contributers are. You will need to use the `contributors_url` for this.
-
-!Important
-- Do not duplicate code! This is especially important for making requests since we are making multiple ones with different urls and we want to do different actions based on the call we are making. Here are some handles to get you started:
-  - So write a function called `makeRequest` which accepts (at least) the following parameters: `url` and `callback`.
-  - Make sure your `callback` is called when the request errors or when it sends a response (look at the documentation)
-  - Your `callback` functions should accept two parameters so it can handle both errors: `err` and `response`.
-  So based on your users actions (input, hovering, clicking) you want to call `makeRequest` with a different `url` and supply it with a function that handles both errors (display an error message to the user for example) and responses (render it correctly, as described below). 
- - Make your functions small and reusable (modular)! That means create separate functions to handle certain steps. 
-
-11) GO WILD
-
-Again, check out the Github API documentation to see what kind of magic stuff you can do with it.
-
-The assignment is to implement something extra that is not in the assignment :scream: (nice and vague right?)
-
-So for example, we have teams in our organization. You can find out who are in there and make a call to 'https://api.github.com/users/' + userInput (where userInput is a string typed into a search field by a user). You can show the users name, avatar image (not the link to the image!) and the number of public repos they have. Or you could make an API call to 'https://api.github.com/users/user/repos' to find out the public repo's they have. Or you can show how many people starred a specific repository. 
-
-Anyway, endless fun and possibilities. Need inspiration, check out the Github API documentation. Oh and please make it look nice (hint: use the stuff you learned in HTML/CSS)!
 
 ### Step 5: **Some freeCodeCamp challenges:**
 
diff --git a/Week8/MAKEME.md b/Week8/MAKEME.md
@@ -100,8 +100,69 @@ data = data.map(function (x) { return x * 8; });
 writeDataToFile(data);
 ```
 
+### Step 5: SPA :sweat_drops:
+You are going to write a SPA (Single Page Application) that uses the [Github API](https://developer.github.com/guides/getting-started/). Make sure that your app uses a logical pattern just like [this codepen](http://codepen.io/Razpudding/pen/MmVpeW).
 
-### Step 5: Read before next lecture
+Just like last week:
+
+Make a website that fetches (= to get) data asynchronously.
+
+1) Create a new website with external js file
+
+2) Add a button (e.g. 'click me') that when clicked `console.logs` 'you clicked me!'
+
+3) Create a function that fetches from [The Github API](https://developer.github.com/v3/). For example from [this page] (https://api.github.com/orgs/HackYourFuture/repos). For help on this check this [SO post](https://stackoverflow.com/questions/247483/http-get-request-in-javascript)
+
+4) Display the data that you get from the Github API on your web page.
+
+5) Now link the two together: When you click the button -> get the data from the Github API and display it on your website
+
+Cool we are back where we left of.
+
+6) Take a look at this:
+
+```js
+https://api.github.com/repos/HackYourFuture/CommandLine
+```
+
+7) Make a function which takes a single argument. The function should make an XHR request to `https://api.github.com/repos/HackYourFuture/[SearchTerm]` where the search term will be the argument. This argument will be the input the user has given you, so make sure that when the user clicks the button you call this function with the argument. 
+
+8) Make all the repositories link their own page in Github. Use the value of the key: `name` to make this work (hint: Github urls always look like this https://api.github.com/repos/HackYourFuture/[repositoryName] where [repositoryName] would be replaced by the actual `name` of the repository, for example `CommandLine`). Make sure the link opens in a new tab.
+
+- Make sure you handle user input well. That means you need to think about empty input, and input that doesn't yield any results.
+
+So Github has this really nice documentation :octocat: :
+Check these out for example
+https://developer.github.com/v3/repos/collaborators/
+https://developer.github.com/v3/repos/commits/
+
+9) Extend your page with an input element. This is so the user will be able to type in text.
+
+10) For each repository, show (in the right column) who the contributers are. You will need to use the `contributors_url` for this.
+
+!Important
+- Do not duplicate code! This is especially important for making requests since we are making multiple ones with different urls and we want to do different actions based on the call we are making. Here are some handles to get you started:
+  - So write a function called `makeRequest` which accepts (at least) the following parameters: `url` and `callback`.
+  - Make sure your `callback` is called when the request errors or when it sends a response (look at the documentation)
+  - Your `callback` functions should accept two parameters so it can handle both errors: `err` and `response`.
+  So based on your users actions (input, hovering, clicking) you want to call `makeRequest` with a different `url` and supply it with a function that handles both errors (display an error message to the user for example) and responses (render it correctly, as described below). 
+ - Make your functions small and reusable (modular)! That means create separate functions to handle certain steps. 
+
+11) GO WILD
+
+Again, check out the Github API documentation to see what kind of magic stuff you can do with it.
+
+The assignment is to implement something extra that is not in the assignment :scream: (nice and vague right?)
+
+So for example, we have teams in our organization. You can find out who are in there and make a call to 'https://api.github.com/users/' + userInput (where userInput is a string typed into a search field by a user). You can show the users name, avatar image (not the link to the image!) and the number of public repos they have. Or you could make an API call to 'https://api.github.com/users/user/repos' to find out the public repo's they have. Or you can show how many people starred a specific repository. 
+
+Anyway, endless fun and possibilities. Need inspiration, check out the Github API documentation. Oh and please make it look nice (hint: use the stuff you learned in HTML/CSS)!
+
+_BONUS_ : Code Kata Race
+
+- [Codewars](https://www.codewars.com/collections/hyf-homework-number-2)
+
+### Step 6: Read before next lecture
 
 _Deadline Sunday morning_
 
diff --git a/Week9/MAKEME.md b/Week9/MAKEME.md
@@ -6,7 +6,14 @@ Topics discussed this week:
 • Promises
 ```
 
-## Step 0: Read
+## Step 1: Read
+- If you need to refresh your memory on es6 classes: [es6-classes-in-depth](https://ponyfoo.com/articles/es6-classes-in-depth)
+- Also read this article on scopes & closures: [explaining-javascript-scope-and-closures](https://robertnyman.com/2008/10/09/explaining-javascript-scope-and-closures/)
+
+## Step 2: Feedback
+
+- Create at least 2 issues (bug / feature / code improvement) on another teams github repository. Do this in pairs. 
+-  Solve the issue proposed by another students in your github repo. More info [here](https://hackyourfuture.slack.com/files/michahell/F31BX1XT6/Merging_a_local_branch_into_master)
 
 ## Step 3: Pair programming promises challenge 
 
@@ -19,31 +26,10 @@ So please:
 - Follow the instructions in the REAME of the above repository
 - To hand in your homework you make a PR to the existing repository
 
-_BONUS_ : Code Kata Race
-
-- [Codewars](https://www.codewars.com/collections/hyf-homework-number-2)
-- If you need to refresh your memory on es6 classes: [es6-classes-in-depth](https://ponyfoo.com/articles/es6-classes-in-depth)
-- Also read this article on scopes & closures: [explaining-javascript-scope-and-closures](https://robertnyman.com/2008/10/09/explaining-javascript-scope-and-closures/)
-
-## Step 2: Feedback
-
-- Create at least 2 issues (bug / feature / code improvement) on another teams github repository. Do this in pairs. 
--  Solve the issue proposed by another students in your github repo. More info [here](https://hackyourfuture.slack.com/files/michahell/F31BX1XT6/Merging_a_local_branch_into_master)
-
-### Step 3: Read before next lecture
+### Step 4: Read before next lecture
 
 _Deadline Sunday morning_
 
 Go trough the reading material in the [README.md](/Week9/README.md) to prepare for your next class
 
-<!-- ## Step 3: Pair programming homework/tdd
-
-You will complete the TicTacToe game we started building in class. The code we build in class is available here: https://github.com/HackYourFuture/TicTacToeTDD. 
-One of your teammates should fork the above repo. Work in this repository *together* so you can see who wrote which code. Make a Pull Request to hand in this part of the homework. -->
-
-<!-- rewatch the Hangouts session here: https://www.youtube.com/watch?v=oc9ogCJz9rYs -->
-
->Upload your homework in your "hyf-javascript3" Github repository. Make sure to create a new folder "week3" first. 
-Upload your homework files inside the week3 folder and write a description for this “commit”.
-Your hyf-javascript3/week3 should now contain all your homework files.
-Place the link to your repository folder in Trello.
+>To hand in your homework, make a pull request to the original repository you forked from. Remember, our master branches are protected, you cannot push to a directly cloned repository you first have to make a fork to your own Github.
