Skip to content
This repository was archived by the owner on Jan 14, 2024. It is now read-only.

Commit 8194474

Browse files
committed
2 parents 5cc48bc + 45456df commit 8194474

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

README.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
Like learning a musical instrument, programming requires daily practise.
2+
3+
The exercises are split into three folders: `exercises`, `mandatory` and `extra`. All homework in the `exercise` and `mandatory` section **must** be completed for homework by the following lesson.
4+
5+
The `extra` folder contains exercises that you can complete to challenge yourself, but are not required for the following lesson.
6+
7+
## Instructions for submission
8+
9+
For your homework, we'll be using [**test driven development**](https://medium.com/@adityaalifnugraha/test-driven-development-tdd-in-a-nutshell-b9e05dfe8adb) 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! :)
10+
11+
1. Complete the challenges in each file and save it once you're happy with your changes
12+
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.
13+
3. Raise a PR once you're happy with the quality of your code

0 commit comments

Comments
 (0)