Code Mantra

10 rules I follow in coding

1. Keep searching for a ‘good’ tutorial, ditch it after watching it for 5 minutes or so. Do the search all over, and ditch it again. AVOID this cycle! Watch one until the END. Then, and only then, find another one, to do the same.
2. Watch a tutorial until the end. WRONG. You must watch and ‘type’ the code yourself on your editor. Well, you can even write on a piece of paper, though this will be hard to see the execution of it, but you get the point. Do the job. Write the damn thing down.
3. Understand each LINE and what it does to the code. Each line of code is so important, if it isn’t then it had no reason being there in the first place. So, GET what that line of code does.
4. Pomo-what! Well, there is a Pomodoro technique which goes to about 25–30 minutes of continuous work, and then short break of about 5 minutes, or long break for about 10–20 minutes. Well, this absolutely depends on your rate of understanding something. Some understand things easily, others a little slower. There are other reasons for this, for example, if you’re trying to understand something and it’s not in your first language, it might take you longer than 25–30 minutes of concentration. I use 45 minutes to work on something, and take a 15 minutes BREAK. Then do that again. Reason is that, I take time to understand and do something in the depth that I’m…