5 ms·
It's an educational exercise to take something like Joel's essay, try to understand it in the way raganwald advocates here, and then go and edit it such that al
by jerf 15y ago
It's an educational exercise to take something like Joel's essay, try to understand it in the way raganwald advocates here, and then go and edit it such that all the caveats, simplifications, etc are all explicitly enumerated. After you're done doubling the length, ask yourself if anybody would actually have read the end result.
Having gone through a phase where I tried to write like that, I can tell you two things: First, "no". Second, it's a complete waste of time. Add in the caveat that you don't literally mean that there are 0 software packages sold in that price range, and you will still get flamed for the claim you just disclaimed. A lot of people are sloppy readers and putting in that level of detail is like putting fine detail in your painting for a farsighted person without their glasses.
I've come to view this sort of misunderstanding as an unavoidable tax for trying to communicate with humans. I say "humans" because it's not "English's" fault. Natural language is fuzzy mostly because human ideation is fuzzy. Noticing when English creates fuzziness is a noteworthy event precisely because it is an anomaly in the vast sea of fundamentally fuzzy ideas being expressed in English.
- raganwald 15y agoMay I quote you?
- jerf 15y agoGo nuts. Reload first though because I just tweaked it a bit. :)
- scott_s 15y agoThis 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.
- ChuckMcM 15y agoThis is so true. And the comment about academics is well taken as well. Having had many, many experiences on Usenet back in the day where I would post something, someone would pick out some quibbling points, and I'd respond with more clarity, and they would pick at that, and I'd respond again. Until we had like 4 or 6 postings which ended in "Oh, well if you put it like that I guess." and knowing I had basically said the same thing half a dozen times, lead me to the same conclusion as jerf here. What ever you write, some fraction of the audience won't get it. And some fraction of that group may be inclined to respond. Outside of actual trolling, it is the nature of communication. Especially words only communication, that it is imperfect. Once I realized that I tend to be more like raganwald in that I read something, and if it doesn't make sense to me I try to read it again and see if I can figure it out, like a puzzle.
- analyst74 15y agoThis is gold! I'm past the point to get annoyed with those sort of replies from anonymous Internet users; but I still do get annoyed at times by similar replies from smart people that I know. Now that I read this, I am finally at peace.