|
|
|
|
|
|
by KedarMhaswade
4193 days ago
|
|
|
I would have said reading, until I realized that some things can be made more explicit in the video. But in most cases, it is by reading. Specific examples were I liked videos explaining something better (or perhaps as good as the book) are: Unix System Calls (https://www.youtube.com/watch?v=xHu7qI1gDPA) and Suffix Trees (https://www.youtube.com/watch?v=hLsrPsFHPcQ). A lot depends upon how much effort has been put into making of a video. Codeschool's guide (https://gist.github.com/olivierlacan/4062929) is a great start. One issue I see with books/articles is typos. Not many technical book writers are diligent about typos and outright mistakes and coming up with updates for a book is perhaps hard. I become especially infuriated and it stalls my progress when a particular concept/paragraph written in the book is either wrong or I am confused about it and the author is not immediately reachable for clarification. Same might be true with videos, but many videos are live talks and such mistakes are rarer in those settings. |
|
|
This is why my book is hooked up directly to GitHub. You can ask questions and get clarification with two clicks.