3 ms·

Did you know about Cache-oblivious algorithms when you wrote that essay? My sense is that you did not, otherwise you would have mentioned them in passing and no

Did you know about Cache-oblivious algorithms when you wrote that essay? My sense is that you did not, otherwise you would have mentioned them in passing and noted your (arguably reasonable) objections regarding their practicality. [p.s. I'll 'retract' /g that mea-culpa. Didn't mean it in a literal sense of "apology".]

phkamp 6y ago
Yes, I did know about their existence, and I had even tried to implement one of them myself, but ditched once I realized that patents would preclude its use in FOSS. But I did not think then, and still do not think now, that they are core material in bread&butter CS algorithm courses, I consider them more of a research-curiosity, so I cant say I even thought about bringing them into the article.
- eternalban 6y ago
  Fair disclosure that I studied EE so have second hand insight into what a CS education entails, but my thoughts on the oversight that you noted are that it may be too much to expect that level of knowledge sharing in a 4 year undergrad education. I am reminded of internship and post-doc of physicians working in a hospital. I’m sure you are aware of the prevalent mindset (from blogosphere to actual working environments) that heavily discount the value of experience in a software engineer. What are your thoughts on that?
  - phkamp 6y ago
    I think it is tricky. The claimed "time ~ experience" correlation certainly exists, and in a long established discipline, like plumbing, experience is almost unquestionably a virtue. In a young discipline, such as computers, there is a very concrete risk of confusing experience with not-moving-with-the-times, certainly on the party claiming experience. So it is probably very much a case-by-case judgement call ?
    - eternalban 6y ago
      I think we're on the same page. I consider the state of affairs to be pre-industrial / arts & crafts, at best. The atelier approach did wonders for the arts in the Renaissance. I suppose F/OSS to some mild extent provides some of the same benefits.

phkamp 6y ago

Yes, I did know about their existence, and I had even tried to implement one of them myself, but ditched once I realized that patents would preclude its use in FOSS. But I did not think then, and still do not think now, that they are core material in bread&butter CS algorithm courses, I consider them more of a research-curiosity, so I cant say I even thought about bringing them into the article.

eternalban 6y ago
Fair disclosure that I studied EE so have second hand insight into what a CS education entails, but my thoughts on the oversight that you noted are that it may be too much to expect that level of knowledge sharing in a 4 year undergrad education. I am reminded of internship and post-doc of physicians working in a hospital. I’m sure you are aware of the prevalent mindset (from blogosphere to actual working environments) that heavily discount the value of experience in a software engineer. What are your thoughts on that?
- phkamp 6y ago
  I think it is tricky. The claimed "time ~ experience" correlation certainly exists, and in a long established discipline, like plumbing, experience is almost unquestionably a virtue. In a young discipline, such as computers, there is a very concrete risk of confusing experience with not-moving-with-the-times, certainly on the party claiming experience. So it is probably very much a case-by-case judgement call ?
  - eternalban 6y ago
    I think we're on the same page. I consider the state of affairs to be pre-industrial / arts & crafts, at best. The atelier approach did wonders for the arts in the Renaissance. I suppose F/OSS to some mild extent provides some of the same benefits.