4 ms·

I can't decide whether this is gibberish or just pretentious. You should give up writing until you have learnt to express yourself clearly (and have ideas wort

by epo 13y ago

I can't decide whether this is gibberish or just pretentious. You should give up writing until you have learnt to express yourself clearly (and have ideas worth sharing).

baxter001 13y ago
You know he's quoting Engelbart, right?
allannienhuis 13y ago
/ignore epo
akadien 13y ago
Did someone hack your account? Because that level of irony just can't be so easily lost.
general_failure 13y ago
Well, I am not sure if epo is a troll but he does have a point. If you give the original comment a quick read it sounds like gibberish. The language is very 'heavy' like in academic papers. Academic papers to me are a big turn off and I hardly understand what they say most of the time. It also shows how little of academia reaches the common programmers - they are largely inaccessible. (compare number of papers to numbers that actually end up in real software)
- akadien 13y ago
  Respectfully, the ratio of "papers to systems" has less to do with communication and more to do with tenure and promotion. Most professors couldn't care less if their papers are implemented, or even read.
- nahreally 13y ago
  Academia reaches out to the common programmer and student all the time; they write books. Academic research papers are aimed at other researchers, i.e. people who are up to speed with the concepts and terminology, if you or I don't understand the latest research on machine vision, then though luck, we just lack the necessary background, and that's discounting the fact that we are different audiences and seek for different content and form from each other. How often are we programmers interested in detailed proofs? Or even sketch proofs? If you decide to helpfully include code samples and they are full of boost::this or ApacheFooXMLFactoryThat, would that be of help to an academic who only implements his algorithms in isolation and doesn't know of massive APIs, or to researchers 20 years from now?

by epo 13y ago

I can't decide whether this is gibberish or just pretentious. You should give up writing until you have learnt to express yourself clearly (and have ideas worth sharing).

baxter001 13y ago

You know he's quoting Engelbart, right?

allannienhuis 13y ago

/ignore epo

akadien 13y ago

Did someone hack your account? Because that level of irony just can't be so easily lost.

general_failure 13y ago

Well, I am not sure if epo is a troll but he does have a point. If you give the original comment a quick read it sounds like gibberish. The language is very 'heavy' like in academic papers. Academic papers to me are a big turn off and I hardly understand what they say most of the time. It also shows how little of academia reaches the common programmers - they are largely inaccessible. (compare number of papers to numbers that actually end up in real software)

akadien 13y ago
Respectfully, the ratio of "papers to systems" has less to do with communication and more to do with tenure and promotion. Most professors couldn't care less if their papers are implemented, or even read.
nahreally 13y ago
Academia reaches out to the common programmer and student all the time; they write books. Academic research papers are aimed at other researchers, i.e. people who are up to speed with the concepts and terminology, if you or I don't understand the latest research on machine vision, then though luck, we just lack the necessary background, and that's discounting the fact that we are different audiences and seek for different content and form from each other. How often are we programmers interested in detailed proofs? Or even sketch proofs? If you decide to helpfully include code samples and they are full of boost::this or ApacheFooXMLFactoryThat, would that be of help to an academic who only implements his algorithms in isolation and doesn't know of massive APIs, or to researchers 20 years from now?