@@ -38,19 +38,21 @@ How to use this tutorial
3838you jump right to folder 05 and don't know why there is a ` mov ah, 0x0e ` , it's because you missed lecture 02.
3939Really, just go in order. You can always skip stuff you already know.
4040
41- 2 . Read each README first. Especially the first line, which details the concepts you should be familiar with
42- before reading the code.
41+ 2 . Open the README and read the first line, which details the concepts you should be familiar with
42+ before reading the code. Google concepts you are not familiar with. The second line states the goals for each lesson.
43+ Read them, because they explain why we do what we do. The "why" is as important as the "how".
44+
45+ 3 . Read the rest of the README. It is ** very concise** .
4346
44- 3 . Read the README. It is ** very concise** . The only theory is the required to understand the code and there
45- are tips on what to look at when you open the code file(s)
47+ 4 . (Optional) Try to write the code files by yourself after reading the README.
4648
47- 4 . Look at the code examples. Some times you may be able to write them yourself just from the hints on the README .
49+ 5 . Look at the code examples. They are extremely well commented .
4850
49- 5 . Experiment with them and try to break things. Try to change pointers and registers and see what happens. You know, the usual.
51+ 6 . (Optional) Experiment with them and try to break things. The only way to make sure you understood something is
52+ trying to break it or replicate it with different commands.
5053
5154
52- TL;DR: First read the README on each folder, then decide if you will
53- implement it yourself or just read the provided code files.
55+ TL;DR: First read the README on each folder, then the code files. If you're brave, try to code them yourself.
5456
5557
5658Contributing
0 commit comments