3 ms·
This is why academic writing - even academic writing about cool technical topics - is often "dry." We have to write like that. And it is tiresome to read. But i
by scott_s 15y ago
This is why academic writing - even academic writing about cool technical topics - is often "dry." We have to write like that. And it is tiresome to read. But it's necessary for two reasons. First, it would never get past peer review otherwise. But even if we could eke it past, it's still not a good idea because when someone else goes to replicate or build on what we did, all those details that drag down the writing become mightily important.
I've often thought that people who publish papers should also have a blog, and where they should have a more digestible explanation of their work. Of course, I have not done this. (Yet.)
- praptak 15y agoI remember reading an advice piece on how to read scientific papers. The core of it was that you need to read them breadth first (i.e. skim many times, each time trying to go deeper into the details.) What you have written explains why it is such a good piece of advice - if you read a paer depth first you'll get bogged in the details without a chance to get the whole picture.