Should I read papers?
📜 Abstract
My answer to the question “Should I read papers?” is a resounding yes, but really what I mean is: you should stretch. Give yourself a challenge. There’s more beneath the surface than you could ever imagine.
✨ Summary
This HTML article is an editorial rather than a conventional research paper. Bernstein argues that software developers and other practitioners should engage with research papers, but that “reading” need not mean reading every word from beginning to end. He presents skimming references, investigating authors, and understanding a paper’s domain from its abstract as legitimate forms of engagement. The central argument is that papers should be approached as continuing relationships with ideas and their authors, and that readers should not be intimidated by unfamiliar material. (michaelrbernste.in)
The article’s documented influence appears limited to recommendation and inclusion in software-engineering and research-reading resources rather than direct influence on scholarly research or industry practice. It is listed in the Papers We Love reading guide and in the Software Papers curated reading list, and it has also been linked in online discussions about reading technical papers. No substantial scholarly citation trail or concrete industry adoption attributable to this article was found. (github.com)