4 ms·
Good point. In the article I also point out that you should not be reading code passively. You should be running the tests, executing the code, breaking stuff,
by sant0sk1 16y ago
Good point. In the article I also point out that you should not be reading code passively. You should be running the tests, executing the code, breaking stuff, and trying to fix it.
- j_baker 16y agoI noticed that. Perhaps my point is more of a semantic one. It still seems to me that the article seems to focus more on the reading than the modifying though.