Today I'm starting my journey to becoming a JavaScript Code Warrior on CodeWars.
For the next 30 days I will be solving 3 coding challenges, or kata, a day, as well as writing 3 possible solutions for each kata solved. The first solution will be the simplest and most readable, followed by an intermediate one and ending with the most complex or advanced solution, which will often be a one-liner. It should go without saying, but all solutions will be written in JavaScript.
Each day, I'll write a post discussing the kata of the day where I break down the problems using the P.R.E.P. technique. P.R.E.P. stands for Parameters, Returns, Examples and Pseudo Code and is an effective technique to use when solving coding challenges, especially for beginners who struggle with this. Of course I will also provide the 3 solutions mentioned above, with details on each of the implementations.
Important note:
I debated very heavily on the ethics of writing these posts, since I am aware they can be used for cheating purposes, which is against CodeWars' Code of Conduct - rightfully so. In fact, the Code of Conduct also discourages sharing solutions on GitHub, since it makes it easier for Code Warriors to look for a solution rather than putting in the work to complete the challenge themselves.
However, while I understand their very valid concern, my posts will be focusing more on the process of solving the challenges and different approaches that can be taken, instead of just simply providing the solutions. These posts are for those of you that get stuck when trying to solve a challenge, have no idea how to go about breaking down the problem and/or are having issues understanding some of the (more complicated) alternative solutions that are provided after solving a challenge.
That said, I do HIGHLY encourage you to try to solve/understand the challenge yourself first and if you get really stuck, these resources are here to help you get unstuck.
Top comments (0)