Skip to content

Instantly share code, notes, and snippets.

@luigisayshello
Last active January 3, 2020 14:41
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save luigisayshello/11177050 to your computer and use it in GitHub Desktop.
Save luigisayshello/11177050 to your computer and use it in GitHub Desktop.
How to learn to code by doing and usign tutorials
Common Rules:
-Speedread the chapter
-Do not copy-paste: Copy/pasting allows you to avoid thinking. If you don't think about WHY and HOW your code works, of course you won't get anything. If you make yourself type the code yourself every time, you are forcing your brain to think about it and process it, so you'll be more likely to remember it without googling next time.
If you copy-paste comment the code explaining what it is doing in that line.
-Create a common typos/errors list: When you type the code, probably you will copy something wrong, or forget something, so when you do just add the error/typo that you made and put somekind of counter ( ||||\ or xxxxx or 12345) to measure the frequency. Now, whenever you get an error you can use this list to check if it's not a common typo.
-Commands list: Create a list of common commands and the most used commands in a certain language.
-Concepts file: When you learn a new concept read, explain to yourself, outloud -> try -> explain with your own words (inside file).
You should memorize, but not by rote - rather, memorize by learning the concepts. If you do not understand concepts, you may want to do some reading about how the different objects you are using fit together.
-Create a hack side project:
-Try to create a side project during the tutorial so that you can apply what you are learning in your own project. It could be identical (it should be) but just scretch a little more everytime, just go foward and hack a little.
-Let your tutorial project prestine, so you don't have to spent to much time solving bugs that you don't have a single Idea on how to solve. If your sideproject breaks, you can continue to learn and probably you will find a solution, but you will not morgage your learning progress by it.
-Just do something little from scratch for every new thing that you learn, example: You are learn how to do tables in Html, so you just do a bunch of tables using all the techiques available.
-Explore.
If you procrastinate a lot (like me), just use the pomodoro,
1) Before more, use 1 click (25 minutes) to see what you will be doing, and speadread the chapter that you will start
2) Then just make one click (1 cycle 25 minutes) only focused on the chapter.
P.S. With some of the techniques that I advise you to follow, you probably will fell that you are taking to long than you should, it's true, but if you don't do this, you will spent a shitload of time trying to figure out where the fuck did you spent 3 weeks on, because you don't know shit, and you don't remember shit.
With this you will learn much more faster and you will not spent a big deal of time trying to reunderstand what you should already know.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment