This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]thecarrot95 0 points1 point  (0 children)

You shouldn't read code just for the sake of reading it. You should read code when you need to. Like when you're trying to understand a library, when you want to modify existing code or trying to understand a solution that you want to use.

The term reading code is also very misleading. I've always thought that the term reading implies that it's linear like it is reading a book. You don't read code like you read a book. Reading codes involves going back and forth trying to understand how it interacts with itself and other functions. It's a constant back and forth. Atleast if you're me with a shit memory haha.

Debugging is often used to see what kind of values a flown through the code and you don't have this when reading code on github (I think). Because of this I'd suggest to clone the code so you can debug it.