4 ms·
The implication that I get from the quote is that people don't read code for the sake of reading code. And that matches my experience: When I read code, it's p
by majewsky 10y ago
The implication that I get from the quote is that people don't read code for the sake of reading code.
And that matches my experience: When I read code, it's precisely because the documentation is lacking, or because I want to match up an error message produced by the code with the logic preceding the error message's origin.
- vog 10y agoOr, quite often, you read it because you want to change it - to extend it or to fix a bug.
- kakarot 10y agoI think the best way to both read code and gain experience is to set a goal of at least weekly or monthly contributions to a couple of open codebases that benefit your life.
- emodendroket 10y agoBut if you look at the article you'll see what I think is a salient point -- looking at code and figuring out how it works often looks more like an "investigation" (like, set some breakpoints and step through it, for instance). It's nothing like sitting in front of a fireplace with a novel.
- joshuamorton 10y agoChoose your own adventure books are still reading though. I think that there's also a much more similarity with analyzing a novel than reading one for pleasure. Reading code has a much greater mental tax than pleasure reading, it requires more focus to actually put together what's going on, and that's similar to analyzing a novel for a report, where you might read the same passage 4-5 times, taking notes. Or even better yet, analyzing a poem, which are often short (and often obey 80 char line width rules!) and analyzing them can require a great amount of focus and thought to decide why a poet used this word in this way, and what meaning they intended to convey and such. That's much more similar to reading code than reading a novel, and I expect also less common.