Skip to content

Commit e74007b

Browse files
author
eoinnoble
committed
Reorganise/update text, expand Codewars section
Apart from grammar, punctuation and stylistic changes, the document was unclear about where to find the Codecademy forum and didn’t explain Codewars in enough detail for new coders. There was also some repetition between sections that I have collected into a general tips section at the end of the document.
1 parent 8410262 commit e74007b

File tree

1 file changed

+23
-14
lines changed

1 file changed

+23
-14
lines changed

README.md

Lines changed: 23 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,36 @@
1-
#Learning JavaScript with Codewars & Codecademy.
1+
#Learning JavaScript with Codewars & Codecademy
22

3-
[Codecademy](https://www.codecademy.com) and [Codewars](https://www.codewars.com) are two fantastic resources for learning JavaScript. Whether you are looking to apply to Founders & Coders (in which case they are necessary) or simply just want to learn, completing Codecademy’s JavaScript course and then solving some katas on Codewars is a great learning route. Good as these resources are, if you are new to programming, they are not always 100% straightforward and can leave you confused. Here are some tips on what to do when you get stuck.
3+
[Codecademy](https://www.codecademy.com) and [Codewars](https://www.codewars.com) are two fantastic resources for learning JavaScript. Whether you are looking to apply to Founders & Coders (in which case they are necessary) or just want to learn, completing Codecademy’s JavaScript course and then solving some katas on Codewars is a great learning route. Good as these resources are, if you are new to programming, they are not always 100% straightforward and can leave you confused. Here are some tips on what to do when you get stuck.
44

55

66
##Codecademy
77
If you are completely new this the best place to start.
88

9-
1. If you are stuck re-read the info on the side (sounds obvious but I often forgot to do this).
10-
2. Checkout the Q and A forum, people often have similar problems and there are a few bugs which can be picked up here.
11-
3. Use an online code editor like [repl.it] (https://repl.it/) to check your code is working, tweak your code and see if you can get it to behave the way you want.
12-
4. Use google, if you find the answer, read around or play with the code to work out how it works.
13-
5. If a part of Codecademy is confusing you, look online for other resources (youtube, blogs etc) that may explain the concept in way that relates better to you.
9+
1. If you are stuck re-read the info in the side panel (sounds obvious but I often forgot to do this).
10+
2. Check out the Q&A forum (click ‘Get Help’ in the bottom-right of the screen, select ‘I need help with this exercise’ and follow the link to the forum), people often have similar problems and there are a few bugs which can be picked up here. **Warning:** forum posts may contain spoilers.
11+
1412

1513
##Codewars
16-
Once you have some basic knowledge of JavaScript, it’s time to start using your knowledge solving problems on codewars.
14+
Once you have some basic knowledge of JavaScript, it’s time to start using your knowledge solving problems, or “kata”, on Codewars.
1715

1816
1. The tips mentioned above for Codecademy are also useful here.
19-
2. For longer and complex problems, try and break down the problem and write a solution using pseudo code (code in note form - it doesn’t need to run correctly or be syntactically correct) . Write functions or sections of your code in a code editor- this way you break down the problem into smaller parts and can identify where the problem is.
20-
3. GOOGLE EVERYTHING. Seriously. Google pretty much what you have to do for the kata i.e. 'How to turn an array of strings into an array of numbers js'. The answer will be out there somewhere. Mozilla Developer Network (MDN) and Stack Overflow are great websites for this. W3schools also ok but a bit more basic.
21-
4. There are some bugs in Codewars. For example if you are working on a problem that doesn’t have any tests written for it, it may fail to pass its’ tests, but passes ok if you submit it directly.
22-
5. Write your own kata - Codewars gives you lots of credit for this.
23-
6. `console.log()` is often an essential way to help you complete challenges. You’ll often need to see exactly which cases your code is failing at, by using console.log(<your chosen input goes here>) you’ll uncover the often random parameters being passed into your code. You’ll need to hit the run tests or submit button to see the output displayed .
24-
7. Once you have completed a kata and can see the solutions compare yours to the top rated solution. You should spend a little time studying the methods and approaches used in this top solution, as this will help you understand other JavaScript methods and more elegant ways of solving problems that are often more readable.
17+
2. You will start on Codewars at 8 kyu, or “rank 8”, the lowest of ranks, and by completing kata you will level up to the higher ranks. Kata are marked as suitable for particular kyu levels, so if you are at 6 kyu then 6 kyu kata are appropriate to your level, 5 kyu kata will be a stretch, and 2 kyu kata may be out of your league, for example.
18+
3. While you can get to kyu 5, the minimum level required for Founders & Coders, just by doing 8 kyu kata, this is an inefficient use of your time, not to mention completely against the spirit of Codewars! The most efficient way to rank up is to complete kata that are at or just above your own kyu level.
19+
4. [The kata page](https://www.codewars.com/kata/latest/my-languages) offers a number of filters that will save you time:
20+
- Make sure to only work on ‘Approved’ kata, as you will not get credit for completing ‘Beta’ kata.
21+
- Sorting by ‘Positive Feedback’ is a great way to find the best kata on the site, those that are particularly challenging or well written.
22+
- You can filter for different difficulties and language features. Not so hot on your algorithms? Why not filter for some lower kyu ‘Algorithms’-tagged kata to practice on?
23+
- Remember to select ‘Kata I have not completed’ from the ‘Progress’ drop-down so you don’t see completed problems in the list.
24+
5. While the filtering tips above will save you from the most poorly written kata, and 99% of the time the issue will be with your code or with your understanding of the instructions, there _may_ be some kata that contain bugs or were ported over to JavaScript incorrectly. Check the ‘Discourse’ tab to see if anyone else is having trouble with it. It should be clear pretty quickly if there are any bugs with the kata. Posts that contain spoilers are helpfully hidden!
25+
6. Write your own kata - Codewars gives you lots of credit for this.
26+
7. Once you have completed a kata and can see the solutions, compare yours to the top rated solution. Try to spend a little time studying the methods and approaches used in the top solutions, as this will help you understand other JavaScript methods and more elegant ways of solving problems.
27+
28+
##General tips
29+
- **GOOGLE EVERYTHING.** Seriously. If you’re stuck with a particular part of your code just search for the problem. The answer will be out there somewhere, it’s just a matter of formulating the correct question and using the correct terminology. Mozilla Developer Network (MDN) and Stack Overflow are great websites for this. w3schools is ok but a bit more basic. While it can be very tempting just to paste in code you’ve found, it always pays off to try to understand how it’s working – it will save you time later!
30+
- `console.log()` is an essential way to help you complete challenges. You’ll often need to see exactly which cases your code is failing at, or what the value of a variable is at any given stage. Remember you’ll need to hit the run tests or submit button to see the output displayed.
31+
- Use an online code editor like [repl.it] (https://repl.it/) to check your code is working, tweak your code and see if you can get it to behave the way you want.
32+
- For longer and more complex problems, try to break down the problem and write a solution using pseudo code (code in note form – it doesn’t need to run correctly or be syntactically correct).
33+
- Don’t be afraid of pen and paper, it can be invaluable in helping you understand challenging processes like recursion.
2534

2635
##Links
2736
[Ok, so you want to learn how to code.] (https://medium.com/@charlotteis/ok-so-you-want-to-learn-how-to-code-b74bc3ac6107)

0 commit comments

Comments
 (0)