Reading is important. However, the process of reading matters just as much. On the one hand, one doesn't want to miss useful information, on the other, trying to understand and comprehend every word stretches this process to infinity. Next, I will share my way of reading. Most likely, it’s not for everyone, but, as a practice has shown, many people like it.
What is really important when choosing a programming language and how to start learning.
We’re going to tell you the story of Ruslan, who worked in the oil industry in Russia (Ufa) but left everything and moved to the US. He repaired household appliances and drove trucks, then learned Java to become a programmer.
Below are the most common mistakes programmers make when naming variables and functions in their code. These examples are taken from the projects of Hexlet students. I use JavaScript for demonstration purposes only because it is the most universal language, so the examples have nothing to do with the language being used. These mistakes are found everywhere in equal proportions.
What is the most difficult part of being a programmer? Naming variables.
This joke seems to be popular for a reason among programmers. Naming often causes a lot of struggle. And indeed, how we name our entities (functions/variables/constants/classes/modules) is of great significance, because most of the time we read code, not write.
It is very easy to make mistakes when you have to handle variables, change them, keep track, etc. Especially in a loop. A great way to understand what's going on is to use the simplest debugging technique — console.log. This function prints onto the screen whatever you pass to it.
I have a function that iteratively calculates the factorial. The idea is simple: multiply numbers from 1 up to n.
We are launching our new study program in English. The first course — Intro to Programming — has started yesterday, new lessons come out every Tuesday and Friday. It's free!
From zero to a developer. Refunds in case you won't get a job
