HackYourFuture · NoerGitKat · Sep 9, 2019 · Jun 18, 2019 · Jun 25, 2019 · Jul 1, 2019
diff --git a/.DS_Store b/.DS_Store
diff --git a/README.md b/README.md
@@ -1,22 +1,78 @@
+> If you are following the HackYourFuture curriculum we recommend you to start with module 1: [HTML/CSS/GIT](https://github.com/HackYourFuture/HTML-CSS). To get a complete overview of the HackYourFuture curriculum first, click [here](https://github.com/HackYourFuture/curriculum).
+
 > Please help us improve and share your feedback! If you find better tutorials
-or links, please share them by [opening a pull request](https://github.com/HackYourFuture/JavaScript1/pulls).
+> or links, please share them by [opening a pull request](https://github.com/HackYourFuture/JavaScript1/pulls).
+
+# Module #2 - JavaScript 1: Programming Basics (Frontend)
+
+![JavaScript1](./assets/javascript1.png)
+
+In this module you'll make a start into wonderful world of programming. We will be using the programming language `JavaScript` to do so. You'll learn about the basic building blocks of programming: `loops`, `functions`, `control flow` and more. Consider these as the ABC's of programming, without them it's impossible to write working software!
+
+You'll be learning two main things:
+
+1. Fundamental concepts in programming
+   While we're using JavaScript to illustrate these concepts, it's important to keep in mind that what you will learn is applicable to **any** programming language. They might differ in syntax (a fancy term for the arrangement of words in a language in order for it to make sense), but the functionality will be the same: a loop will always be a loop.
+
+   This should be your mindset when you're learning concepts: **I'm learning how to become a software developer that can adjust to any language used, because I know what the underlying principles and concepts are**.
+
+2. How to think like a programmer
+   In one sentence this means: **knowing how to solve problems computationally**. Let's split that up in two parts: `how to solve problems` refers to the ability to identify issues and find effective solutions. `computationally` refers to the ability to think in logical steps that the computer can understand and execute.
+
+   This should be your mindset when you're learning how to think : **I'm learning how to think in logical steps, identifying cause and effect, and always looking for solutions**.
+
+## Before you start!
+
+In order to test your JavaScript code, you'll be using software that will execute your files from the command line. This software is called [Node.js](https://nodejs.org/en/download/). Download the Long-Term Support (LTS) version for your specific operating system.
+
+- For Windows, click [here](https://nodejs.org/dist/v10.16.0/node-v10.16.0-x64.msi)
+- For Mac, click [here](https://nodejs.org/dist/v10.16.0/node-v10.16.0.pkg)
+- For Linux, click [here](https://nodejs.org/dist/v10.16.0/node-v10.16.0-linux-x64.tar.xz)
+
+After you've installed it, go to your command line interface. Type in the following command:
+
+```
+node --version
+```
+
+It should show you version `v10.14.2` or higher.
+
+## Learning goals
+
+In order to successfully complete this module you will need to master the following:
+
+- Have an idea of what computer programming is
+- Know the basic buildingblocks of JavaScript
+- Correctly write and use variables, functions and loops
+- Understand the control flow
+- Think like a programmer
+
+## How to use this repository
+
+This repository consists of 3 parts:
+
+1. `Reading materials`: this document contains all the required theory you need to know _**while**_ you're coding. It's meant as both study material and as a reference to understand what you're doing.
+2. `Homework`: this document contains the instructions for each week's homework.
+3. `Lesson Plans`: this part is meant for teachers as a reference. However, as a student don't be shy to take a look at it as well!
+
+After your first class you should start with checking the `reading materials` for that week. So, for the first time that is the [Week 1 Reading](/Week1/README.md). Study all the concepts and try to get the gist of everything. After, you can get started with the `homework` for that week.
 
-# HackYourFuture - JavaScript 1
+If you have any questions or if something is not entirely clear ¯\\\_(ツ)\_/¯, please ask/comment on Slack!
 
-Here you can find course content and homework for the JavaScript 1 module
+## Planning
 
-|Week|Topic|Read|Homework|
-|----|-----|----|--------|
-|1.|Git Session|[Reading Week 1](/Week1/README.md) | [Homework Week 1](/Week1/MAKEME.md)|
-|2.|• Intro JavaScript (What is it, where can you use it for)<br>• [Variables (var, let, const)](../../../fundamentals/blob/master/fundamentals/variables.md)<br>• [Basic Data types (Strings, Numbers, Arrays, Booleans)](../../../fundamentals/blob/master/fundamentals/values.md)<br>• [Operators](../../../fundamentals/blob/master/fundamentals/operators.md)<br>• [Special characters and their names](../../../fundamentals/blob/master/fundamentals/names_of_special_characters.md)<br>• [Naming conventions](../../../fundamentals/blob/master/fundamentals/naming_conventions.md)|[Reading Week 2](/Week2/README.md)|[Homework Week 2](/Week2/MAKEME.md)|
-|3.|• Git work flow :smiling_imp:<br>• [Advanced data types (objects)](../../../fundamentals/blob/master/fundamentals/objects.md) <br>• [Conditional execution](../../../fundamentals/blob/master/fundamentals/conditional_execution.md) <br>• [Statements vs Expressions](../../../fundamentals/blob/master/fundamentals/statements_expressions.md)<br> • [Loops (for/while)](../../../fundamentals/blob/master/fundamentals/loops.md)<br>• [Functions](../../../fundamentals/blob/master/fundamentals/functions.md) <br>• [Scope](../../../fundamentals/blob/master/fundamentals/scope.md)|[Reading Week 3](/Week3/README.md)|[Homework Week 3](/Week3/MAKEME.md)|
+| Week | Topic                                                                             | Reading Materials              | Homework                        | Lesson Plan                        |
+| ---- | --------------------------------------------------------------------------------- | ------------------------------ | ------------------------------- | ---------------------------------- |
+| 1.   | What is JavaScript?, Variables, Data Structures & Naming Conventions              | [Reading W1](/Week1/README.md) | [Homework W1](/Week1/MAKEME.md) | [Lesson Plan W1](/Week1/MAKEME.md) |
+| 2.   | Statements vs. Expressions, Control flow, Loops, Operators, Conditional statement | [Reading W2](/Week2/README.md) | [Homework W2](/Week2/MAKEME.md) | [Lesson Plan W2](/Week1/MAKEME.md) |
+| 3.   | Functions, Thinking like a programmer I, How JavaScript relates to HTML/CSS       | [Reading W3](/Week3/README.md) | [Homework W3](/Week3/MAKEME.md) | [Lesson Plan W3](/Week1/MAKEME.md) |
 
-__Kind note:__
+## Finished?
 
-We expect you to __always__ come prepared to the class on Sunday.
+Did you finish the module? Good job! You're doing great!
 
-### Overall
-A good understanding of all the above mentioned topics. Want to check your Knowledge? Go through the [JavaScript Fundamentals README](../../../fundamentals/blob/master/README.md) and research/ ask for help (Slack!) with the concepts that are not entirely clear.
+If you feel ready for the next challenge, click [here](https://www.github.com/HackYourFuture/JavaScript2) to go to JavaScript2!
 
+_The HackYourFuture curriculum is subject to CC BY copyright. This means you can freely use our materials, but just make sure to give us credit for it :)_
 
-*The HackYourFuture curriculum is subject to CC BY copyright. This means you can freely use our materials, but just make sure to give us credit for it :)*
+<a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a><br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.
diff --git a/Week1/.DS_Store b/Week1/.DS_Store
diff --git a/Week1/LESSONPLAN.md b/Week1/LESSONPLAN.md
@@ -0,0 +1,26 @@
+# Lesson Plan Week 1
+
+## Agenda
+
+The purpose of this class is to introduce to the student:
+
+(1) what variables are and why they're used
+(2) what a data type is, and which ones there are in JavaScript
+
+FIRST HALF:
+
+SECOND HALF:
+
+### Core concepts
+
+FIRST HALF (12.00 - 13.30)
+
+1.
+
+SECOND HALF (14.00 - 16.00)
+
+2.
+
+3)
+
+4.
diff --git a/Week1/MAKEME.md b/Week1/MAKEME.md
@@ -1,32 +1,184 @@
-## Homework week 1:
+# Homework JavaScript1 Week 1
 
+## **Todo list**
+
+1. Practice the concepts
+2. JavaScript exercises
+3. Code along
+
+## **1. Practice the concepts**
+
+Before we learn how to build actual applications, we first need to gain experience using JavaScript in a computational way. This teaches us how to think like a programmer, and gives us more experience with the language itself.
+
+In the following exercises you'll learn how to use different JavaScript concepts to solve common computational problems:
+
+- [Learn-js](https://www.learn-js.org/). Do all the `Learn the basics` exercises.
+- [Codecademy: Introduction to JavaScript](https://www.codecademy.com/learn/introduction-to-javascript/modules/learn-javascript-introduction). Do all the exercises (#1 to #10).
+- [FreeCodeCamp: Introduction to JavaScript](https://learn.freecodecamp.org/javascript-algorithms-and-data-structures/basic-javascript). Do at least 20 exercises, you can choose whichever ones you feel are challenging enough.
+
+## **2. JavaScript exercises**
+
+Inside of your `JavaScript1` fork, create a folder called `week1`. Inside of that folder, create a folder called `js-exercises`. For all the following exercises create a new `.js` file in that folder (10 files in total). Make sure the name of each file reflects its content: for example, the filename for exercise one could be `logHello.js`.
+
+> In each file, start off with the string `'use strict'`. This will make sure the code interpreter will enforce stronger rules when looking at your code.
+
+> Before starting, make sure you have [Node.js](https://nodejs.org/en/download/) installed on your computer. You'll use this to execute your code to check if it works.
+
+**Exercise 1: Hello world!**
+
+Write a statement, using the `console.log()` function. Give it a string as an argument. The string should contain the message "Hello world!".
+
+Write 10 statements like these, but in different languages.
+
+For example:
+
+```
+Halo, dunia! // Indonesian
+Ciao, mondo! // Italian
+Hola, mundo! // Spanish
+```
+
+Using the command line, navigate to your `week1` folder and type in the following to test your code:
+
+```
+node FILENAME.js
+```
+
+It should show the message `Hello world!` in 10 different languages.
+
+**Exercise 2: Error debugging**
+
+Consider the following code:
+
+```js
+console.log('I'm awesome');
+```
+
+Copy the code in your `.js` file and run it in the command line using `node`. You will see that you will get a SyntaxError. **Correct the mistake**.
+
+Hint: the SyntaxError message will give you some indication of what the error _might_ be, but figure out yourself how to correct it!
+
+When done right, it should show the message `I'm awesome`.
+
+**Exercise 3: Log the number**
+
+Follow the steps. Make sure that each step is written on the line after.
+
+1.  First, declare your variable `numberX`. Do not _initialize_ it (which means, don't give it a value) yet.
+2.  Add a `console.log` statement that explains in words _what you think_ the value of `x` is, like in this example.
+3.  Add a `console.log` statement that logs the value of `numberX`.
+4.  Now _initialize_ your variable `numberX` with a number (also called an `integer` in computer science terms).
+5.  Next, add a `console.log` statement that explains _what you think_ the value of `numberX` is.
+6.  Add a `console.log` statement that logs the value of `numberX`.
+
+**Exercise 4: Log the string**
+
+Follow the steps. Make sure that each step is written on the line after.
+
+1. Declare a variable `myString` and assign a string to it. Use your full name, including spaces, as the content for the string.
+2. Write a `console.log` statement in which you explain in words _what you think_ the value of the string is.
+3. Now `console.log` the variable `myString`.
+4. Now reassign to the variable `myString` a new string.
+5. Just like what you did before write a `console.log` statement that explains in words _what you think_ will be logged to the console.
+6. Now console.log `myString` again.
+
+**Exercise 5: Round a number and log it**
+
+Follow the steps. Make sure that each step is written on the line after.
+
+1. Declare a variable `z` and assign the number 7.25 to it.
+2. Write a `console.log` statement in which you log the value of `z`.
+3. Declare another variable `a` that has the value of `z` but rounded to the nearest integer.
+4. Write a `console.log` statement in which you log the value of `a`.
+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.
+6. Write a `console.log` statement in which you log the value of the highest value.
+
+**Exercise 6: Log an array of animals**
+
+Follow the steps. Make sure that each step is written on the line after.
+
+1. Declare variable and assign to it an empty array. Make sure that the name of the variable indicates it contains more than 1 item. For example `items` instead of `item`.
+2. Write a `console.log` statement that explains in words _what you think_ the value of the array is.
+3. Write a `console.log` statement that logs the array.
+4. Create a new variable with an array that has 3 of your favorite animals, each in a different string. Make sure the name of the variables says something about what the variable contains.
+5. Write a `console.log` statement that logs the second array.
+6. Add a statement that adds another string ("Piglet)" to the array of animals.
+7. Write a `console.log` statement that logs the second array!
+
+**Exercise 7: Log the length of a string**
+
+Follow the steps. Make sure that each step is written on the line after.
+
+1. Declare a variable called `mySentence` and initialize it with the following string: "Programming is so interesting!".
+2. Figure out (using Google) how to get the length of `mySentence`.
+3. Write a `console.log` statement to log the length of `mySentence`.
+
+**Exercise 8: Type checker**
+
+Write a program that checks the data types of two variables and logs to the console `SAME TYPE` if they are the same type. If they are different types log `Not the same...`.
+
+1. Declare 4 variables: 2 must be `strings` and 2 must be `objects`
+2. Create 8 conditional statements, where for each you check if the data type of one variable is the same as the other
+3. Find out how to check the type of a variable
+4. Write 2 `console.log` statements to log the type of 2 variables, each with a different data type
+5. Now compare the types of your different variables with one another
+6. Log `Not the same...` when the types are different
+
+Here's an incomplete example of how it could look:
+
+```js
+// Declare all variables
+let x = 9;
+let y = 67;
+
+// Check data type
+console.log(...);
+
+// Check if data type is the same
+if (...) {
+    console.log('SAME TYPE');
+}
 ```
-Topics discussed in class this week:
-• Git
+
+**Exercise 9: Log the remainder**
+
+For each of these, write in comments what the answer is followed by how you came to that conclusion
+
+1. If `x` equals 7, and the only other statement is `x = x % 3`, what would be the value of `x` after the calculation?
+2. If `y` equals 21, and the only other statement is `x = x % 4`, what would be the value of `y` after the calculation?
+3. If `z` equals 13, and the only other statement is `x = x % 2`, what would be the value of `z` after the calculation?
+
+**Exercise 10: Compare arrays**
+
+1. Declare 2 variables, that each hold an array. The first array should have 4 items, the second 7 items
+2. Find out how to get the length of each array. Write a `console.log` statement that shows the length of each array
+
+```js
+const array = ["hello", 123, true, { name: "Noer" }];
+
+console.log('The length of the array is...' + ...);
 ```
 
-> [Here](/Week2/README.md) you find the readings you have to complete before the second lecture.
+3. Write a conditional statement that checks if both are of equal length. If they are, log to the console `They are the same!`, if not log `Two different sizes`
+
+## **3. Code along**
+
+We don't want to lose the connection with HTML/CSS, so in the following tutorial you'll learn how to build a simple web application use HTML/CSS and JavaScript.
+
+You'll first write the HTML and CSS, to provide structure and style to the page. When doing so, keep notice of how the developer chooses to do this. Why do they use this tag instead of something else? Why do they give an element a certain class name?
 
-## Step 1: Share a useful resource
+After, the developer will write JavaScript code. You'll notice it's different from how you've used JavaScript. It is something we call **DOM Manipulation**. Don't worry, you don't need to master this just yet. Just follow along and do some research yourself if you already want to learn more about it!
 
-_Deadline Monday_
+- [Calculator](https://www.youtube.com/watch?v=6v4vBXL-qkY)
 
-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 HTML/CSS. 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).
+## **SUBMIT YOUR HOMEWORK!**
 
-## Step 2: Git homework
+After you've finished your todo list it's time to show us what you got! Starting from this week you'll be submitting all your homework through GitHub. What you'll be doing is upload all your files to a forked repository (a copy from the original, which in this case is the [JavaScript1](https://www.github.com/HackYourFuture/JavaScript1) repository) using GIT.
 
-_Deadline Wednesday_
+Take a look at the following [guide](../hand-in-homework-guide.md) to see how it's done.
 
-Git homework for this week:
+The homework that needs to be submitted is the following:
 
-Pair up with another student in your class. The homework requires two people to work together. Let's call them admin and user.
+1. JavaScript exercises
 
-1. admin creates a new repository on github called **animals**.
-2. admin adds a file called “zoo.txt” with some animals generally found in a zoo.
-3. admin commits and pushes the changes (in master branch).
-4. user forks the repository created by admin and bring it to their machine (covered during classwork).
-5. user makes a new branch called user-dev.
-6. user adds another file called “pets.txt” with some animals generally found in a home.
-7. user commits and pushes his branch to remote.
-8. user creates a pull request(PR) to merge changes from user's _user-dev_  branch to admin's _master_ branch.
-9. admin reviews the pull request and approves and merges changes.
+_Deadline Saturday 23.59 CET_