3 ms·
I think "reading code" is actually the easier part of reading code. The hard parts are (1) understanding the scenarios the code covers, (2) interpreting error
by munchbunny 8y ago
I think "reading code" is actually the easier part of reading code.
The hard parts are (1) understanding the scenarios the code covers, (2) interpreting error messages and edge cases coming from it.
- radus 8y agoI think that to some extent those things are implied by "reading", just as some level of comprehension is assumed when talking about reading a book.
- JadeNB 8y ago> I think that to some extent those things are implied by "reading", just as some level of comprehension is assumed when talking about reading a book. Even better, in fact: one can misread a book with, usually, no reasonable way of determining the extent of one's misreading (see https://news.ycombinator.com/item?id=18380366 https://news.ycombinator.com/item?id=18380366 for a current front-page example); whereas, when one (mis)reads code, there is always at hand a way to test the accuracy of one's reading (and perhaps find out thereby, in the presence of a sufficiently detailed specification, that the programmer also 'misread' it!).