> 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 un

> 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)