Inital commit

Author: ChrisOwen101

.DS_Store

@@ -0,0 +1,10 @@
+# Your Details
+
+Your Name:
+Your City:
+Your Slack Name:
+
+# Homework Details
+
+Module:
+Week:

.github/pull_request_template.md

@@ -0,0 +1,3 @@
+node_modules/
+package.json
+package-lock.json

.gitignore

@@ -0,0 +1,10 @@
+# Instructions
+
+Before you start your homework you should make sure you have created a branch for your work.
+
+You can find instructions for submitting your homework here.
+
+- Github Desktop: https://docs.codeyourfuture.io/students/guides/submitting-homework
+- Command Line: https://docs.codeyourfuture.io/students/guides/making-a-pull-request
+
+You should create a new branch for each week of your homework

BEFORE_YOU_START.md

@@ -0,0 +1,43 @@
+# Guidelines
+
+## Week Mapping
+
+This repository has an unusual numbering system compared to the weeks we teach
+
+- JavaScript Core 1 Week 1 -> `Week 1`
+- JavaScript Core 1 Week 2 -> `Week 2`
+- JavaScript Core 1 Week 3 -> `Week 3`
+- JavaScript Core 2 Week 1 -> `Week 4`
+- JavaScript Core 2 Week 2 -> `Week 5`
+- JavaScript Core 2 Week 3 -> `Week 6`
+- JavaScript Core 3 Week 1 -> `Week 7`
+- JavaScript Core 3 Week 2 -> `Week 8`
+- JavaScript Core 3 Week 3 -> `Week 9`
+
+TO DO - Move each of these into their own folder corresponding to their module number and rename to be more sensible. This must be done while students are not working on the repo to avoid conflicts.
+
+## Reviewing students homework
+
+1. Go to https://github.com/CodeYourFuture/js-exercises/pulls
+2. Find the PR opened by the student you are designated to help
+3. If your student has not opened a PR, ask them to open a PR following the instructions in the README
+4. Assign yourself to your student's PR so that other mentors know that your student has a reviewer
+5. Go to the files tab in the PR and start a review. The review should contain:
+
+- Inline comments that:
+  - Praise the student for showing initiative or creativity beyond the lesson
+  - Point out mistakes or bad practises
+  - Explain problems that could be caused by bad code
+  - Ask why a solution might not work
+  - Offer pointers or tips for a better solution
+- An overall comment (when you click the review changes button) that:
+  - Praises the student for their effort/progress
+  - Let's them know if you've asked them to make changes
+  - Highlights any themes that need particular attention, if necessary
+
+6. Submit the review. As long as the student has attempted the homework, choose the option to accept changes so that they get a nice green tick (even if you are suggesting changes).
+7. Add a label to the PR saying `reviewed`
+
+Example PR review: https://github.com/CodeYourFuture/js-exercises/pull/23#pullrequestreview-100326735
+
+Note: this review was written for a student who was advancing quickly so the comments and suggestions to learn additional language features are tailored accordingly.

MENTORS.md

@@ -0,0 +1,28 @@
+# JavaScript exercises
+
+1. Fork this repo
+2. Clone it to your machine
+3. Open it in your code editor.
+4. In the terminal, run this command to add CodeYourFuture as an `upstream` remote.
+   `git remote add upstream git@github.com:CodeYourFuture/js-exercises.git`
+5. Run the command `git remote -v`. You should have two remotes:
+
+* `origin` pointing to your github repo, and
+* `upstream` pointing to CodeYourFuture
+
+During the class (and for homework), we will go through each folder, reading the README and completing the exercises.
+
+For **homework**, we expect you to `add` and `commit` your changes, and `push` them to your own repo (`origin`). You will then need to open a `pull request` so we can review your code.
+
+### Opening a pull request
+
+A pull request is a request to merge one branch into another. In this case you will request to have the `master` branch of your repo, merged into the `master` branch of this (`upstream`) repo.
+
+We won't actually merge your branch, but the pull request will allow us to view and comment on your work.
+
+1. Add the files you have changed using `git add .`
+2. Commit your changes using `git commit` (you can add and commit changes multiple times as you complete exercises)
+3. Push your changes to your own repo using `git push` (this automatically pushes to the `origin` remote)
+4. Go to https://github.com/CodeYourFuture/js-exercises and click the **New pull request** button (this create a request to merge your `origin/master` to our `remote/master`)
+5. Give your pull request a title e.g. `Daniel's homework`
+6. Click **Create pull request**

README.md

@@ -0,0 +1,24 @@
+# Homework
+
+Like learning a musical instrument, programming requires daily practise.
+
+The exercises are split into two folders: `mandatory` and `extra`. All homework in the `mandatory` section **must** be completed for homework by the following Sunday. The `extra` folder contains exercises that you can complete to challenge yourself, but are not required for the following Sunday.
+
+## Instructions for submission
+
+For your homework, we'll be using **test driven development** to check your answers. Test driven development (or TDD) is the practice of writing tests for your code first, and then write your code to pass those tests. This is a very useful way of writing good quality code and is used in a lot of industries. You don't have to worry about knowing how this works, but if you're curious, engage with a volunteer to find out more! :)
+
+1. Complete the challenges in each file and save it once you're happy with your changes
+2. Run the script to check the results against the tests - all tests should read PASSED if you completed the challenges correctly. If a test reads FAILED, find the associated test to identify which function failed and fix it.
+3. Raise a PR once you're happy with the quality of your code.
+   - You can find out how to do this [here](https://docs.codeyourfuture.io/students/guides/submitting-homework)
+
+## Reading List
+
+To challenge yourself even further, you can get ahead for next week's class by reading some of the below documentation:
+
+- [ ] Loops in JS: https://javascript.info/while-for
+- [ ] Switch statements: https://javascript.info/switch
+- [ ] Comparisons in JS: https://javascript.info/comparison
+- [ ] Logical operators in JS: https://javascript.info/logical-operators
+- [ ] More on operators: https://javascript.info/operators

week-1/Homework/README.md

@@ -0,0 +1,13 @@
+There are some tools that will help you to write code. One of these, [Prettier](https://prettier.io/), formats your code, making it easier for you and others to read.
+
+### 1. Install prettier
+
+* In Visual Studio open the extensions panel (see https://code.visualstudio.com/docs/editor/extension-gallery#_browse-and-install-extensions)
+* Search for `Prettier - Code formatter`
+* Click install on the top result
+
+### 2. Enable formatting on save
+
+* In Visual Studio open the settings file (see https://code.visualstudio.com/docs/getstarted/settings#_creating-user-and-workspace-settings)
+* Search for `editor format`
+* Set `editor.formatOnSave` and `editor.formatOnPaste` to true

week-1/Homework/exercises/A-setup-ide/README.md

@@ -0,0 +1,18 @@
+It is programming tradition that the first thing you do in any language is make it output 'Hello world!'.
+
+We'll do this in JavaScript, using something called `console.log()`.
+
+Inside of `exercise.js` there's a line of code that will print "Hello world!".
+
+### 1. Run the program
+
+* Open a terminal window
+* Change directory to this folder (`cd week-1/C-hello-world`)
+* Run the program using node (`node exercise.js`)
+
+### 2. Experiment
+
+* Try to `console.log()` something different. For example, 'Hello World. I just started learning JavaScript!'.
+* Try to console.log() several things at once.
+* What happens when you get rid of the quote marks?
+* What happens when you console.log() just a number without quotes?

week-1/Homework/exercises/B-hello-world/README.md

@@ -0,0 +1 @@
+console.log("Hello world");