2 ms·
You'll end up reading code if you work on code. Find something to work on. (I don't know what you should work on.) Just like you can't really learn math just b
by a3n 10y ago
You'll end up reading code if you work on code. Find something to work on. (I don't know what you should work on.)
Just like you can't really learn math just by reading the book, you'll "learn good code" much more effectively if you're working on it and you have to make decisions and judgments to move forward.
- vog 10y ago> You'll end up reading code if you work on code. This. Also, you'll have a more goal-directed path through the code, which is usually more motivating than understanding code for the sake of understanding. Of course, there's always the pitfall that people will start making changes willy-nilly, until the code does roughly what they want, without really understanding anything. But this will vanish as soon as you put higher quality standards to your own work. (e.g. if you want to ensure that it does the correct thing in all edge cases, or if you produce something larger than a quick hack)
- a3n 10y ago> e.g. if you want to ensure that it does the correct thing in all edge cases, or if you produce something larger than a quick hack) ... if you submit your code to the project's owner. :)
- emodendroket 10y agoBut you'll notice this is nothing like the idea of "reading code" for the sake of it.