writing for a specialized audience
Dec. 23rd, 2009 02:15 pmRight now I'm reading William Cohen's book "A Computer Scientist's guide to Cell Biology", and I find the delivery to be very efficient (though I have little to compare it with), probably because he takes an informational perspective, and isn't shy about using CS concepts and terminology.
You know the "X for dummies" collection? I'd love to see some "X for geeks" series. It could be specialized into "X for mathematicians", "X for Computer Scientists", "X for type theory geeks", etc.
According to Sussman, the legacy of Computer Science is its formal language:
I suspect that, when most scientists speak this "language", we will see greater understanding across disciplines. This is already happening.
---
Tangentially, I'd like to see a book on how to cope with "bad" programming languages, all the while being a hygienist. e.g. tricks for emulating a type system, etc.
You know the "X for dummies" collection? I'd love to see some "X for geeks" series. It could be specialized into "X for mathematicians", "X for Computer Scientists", "X for type theory geeks", etc.
According to Sussman, the legacy of Computer Science is its formal language:
<< Computer Science is not a science, and its ultimate significance has little to do with computers. The computer revolution is a revolution in the way we think and in the way we express what we think. >>
I suspect that, when most scientists speak this "language", we will see greater understanding across disciplines. This is already happening.
---
Tangentially, I'd like to see a book on how to cope with "bad" programming languages, all the while being a hygienist. e.g. tricks for emulating a type system, etc.