- Variables and constants
- Loops in programming
- Arrays and functions
- Where to go from here?
Wow! You finally made it here! Most people do not follow up on their passions and drop the courses they take after only a few tutorials, and this is only the case if they start acting on it!
This way you can see your progress and see the parts where you understand really well, which may have intimidated you at first, as well as catching the parts that you may have ignored or missed.
Throughout the series we have also incorporated a lot of coding best practices. These best practices make your life easier when you are just starting out, and they even become more valuable when you start working or collaborating with other people. And exactly for that reason, there are even standards and sayings like “All code should look like it is written by one person, no matter how many people have collaborated.” This is exactly why, one of the very first concepts, we have seen was commenting our code. Doing this, not only makes you a better programmer in the future, but it also allows you to have a better coding experience when you are starting out as well.
Variables and constants
Loops in programming
Next, we discovered loops in programming. We saw that with using loops we can start avoiding repeating ourselves in code. This basically allowed us to partially start being DRY. This stands for Don’t Repeat Yourself.
Generally speaking, we do not want to write code more than we have to, to complete the task. Because every time we write more code, we introduce more opportunities for errors in code. It takes more time and effort to write more code, introduces potential errors, it is usually not efficient since now you have to save the same code maybe 10 times. And overall it can significantly decrease the coding experience. This is why starting with the while loops and for loops, we started cutting out potentially repetitive code.
Arrays and functions
We have seen that there are two main kinds of functions. One of them being pure functions, the other type being impure functions. Generally speaking, whenever we can, we should aim to use pure functions compared to impure functions. This way, the pure functions we write will behave the same way and will give us the same results, no matter where we run the code, or when we run the code.
Next, we have seen objects. We learned that objects are good at storing highly associated data that can have many dimensions. We started with the simplest way to create objects and moved our way up to creating blueprints for the objects and then creating multiple objects from that blueprint. Using these blueprints allows us to make sure that the fields in objects follow the same guidelines and have the same fields. This way at the end of the day we can be sure that we have a much more uniform database to work with. It also allowed us to write significantly DRY code.
Where to go from here?