| Tags | skill/problem_solving |
| Hard Prerequisites | |
| IMPORTANT: Please review these prerequisites, they include important information that will help you with this content. | |
|
|
It’s time to write some code :)
This is how the challenges work:
Start Project button on your board), we will create a new github repo for you. If you start 5 coding challenges then you’ll have 5 repos.We have a bot 🤖 that plugs into the repos we create. It will mark your work and it will tell you if your code works or not.
If your code doesn’t work then you can try again as many times as you want 😄
However, it’s important that you write code in a very intentional way. You shouldn’t just make random changes to your code and chuck it at the bot until it works.
Make sure you:
Bots are pretty stupid so if you put your code in the wrong place it will tell you that your code doesn’t work. So you need to be very careful about naming things EXACTLY as required. This should be very easy to get right, it just takes a little bit of attention to detail.
Good coders pay close attention to detail and read specifications properly.
If you write a function then you should be able to run the function on your own computer or phone. This is really important. If you submit a function that doesn’t work then you will get a negative review and you’ll have to try again.
Running the code on your own device is:
The fastest way to see if your code is broken is to run it yourself. If you submit guesswork then that would actually be a waste of your time.
Coders are able to test that their own code works. This is a skill you can and should start developing now.
If you write a function and it takes arguments then think about all the different arguments you could pass it. Try to come up with strange situations and make sure that your function works in those situations. For example if your function takes in a number then can it handle positive numbers, negative numbers and zero? If your function takes in a string then what happens if the string is empty? And what happens if the string is really long?
Think about how your code is meant to work and test drive it yourself before handing it in.
Hand in code that you believe in. Show pride in your work!
The bot works by passing a bunch of different values to your functions and then expecting your functions to do very specific things. It will test your code against a lot of different inputs.
If your code fails a test then the bot will give you an example of the kind of input it is testing things against. Consider it a hint. Try to think of other things you can do to test your code out before asking the bot for another review.
We are looking for people who can think for themselves. If you need the bot to do your thinking for you and tell you all the different ways you can test your code out then this bootcamp would not be a good test of your abilities.
We do keep track of the number of times negative reviews are left for each person in the bootcamp. People who are more able to test their own code do better in this career. So please be prepared to think!
We have organized the tasks from the easiest to the hardest. So it would make sense to try to do them in order. But you can really do them in whatever order you want.
Your final score will be calculated according to how many tasks you finish. That means that if the code doesn’t do what it is meant to then it doesn’t count.
If you get feedback on a task it would be really good for you to address that feedback and resubmit that project before starting anything else.
By addressing feedback as quickly as possible you learn as quickly as possible. And learning from feedback will stop you from making the same mistakes over and over.
Good luck!