I regularly hear coders say they cannot understand other people's code so they _had_ to write it themselves. Most people can't read papers either it seems.
People lost ability to read anything longer than a tweet with focus and comprehension. Especially new developers.
I know this because whatever I put in third and further paragraphs of my tickets is not being red or understood.
I sometimes quiz guys on review meetings and I even sometimes put the most important information somewhere in the middle of the ticket. Always with the same result -- they are surprised.
Now, to read a paper is to try to imagine being the person who wrote it and appreciate not just written text but also a lot more things that are not necessarily spelled.
The same with code -- when I read somebodys code I want to recognize their style, how they approach various problems. Once you know a little bit about their vocabulary you can really speed up reading the rest because you can anticipate what is going to happen next.
Comments
I regularly hear coders say they cannot understand other people's code so they _had_ to write it themselves. Most people can't read papers either it seems.
Well, that's another thing.
People lost ability to read anything longer than a tweet with focus and comprehension. Especially new developers.
I know this because whatever I put in third and further paragraphs of my tickets is not being red or understood.
I sometimes quiz guys on review meetings and I even sometimes put the most important information somewhere in the middle of the ticket. Always with the same result -- they are surprised.
Now, to read a paper is to try to imagine being the person who wrote it and appreciate not just written text but also a lot more things that are not necessarily spelled.
The same with code -- when I read somebodys code I want to recognize their style, how they approach various problems. Once you know a little bit about their vocabulary you can really speed up reading the rest because you can anticipate what is going to happen next.
People may have a preference for certainty.
They work on the problem. They will make progress and likely solve it.
They search the literature they will spend time on research and quite possibly lose days before emerging with nothing to show for it.
I see you prefer lousy results.
Also, you read BEFORE you need it.
To be literate, educated, knowledgeable developer. And to know where the knowledge is when you need it (because you can't remember everything).
I wasn’t stating a preference merely observing another possible reason people don’t research solutions before diving in.