Earlier quoted context omitted.
Raymond's "Cathedral" post is a contender for one of the most overrated pieces of technical writing. "The parts that are interesting are not new, and the parts that are new aren't good". It's justifiably infamous for the now-discredited "Linus's law", about "many eyes making all bugs shallow", but large parts of it are also shoplifted from Brooks and Pike. I think it's remembered fondly mostly because it was an effec…
I feel like security bugs are in a class of their own and need different ways of thinking about them. If you leave aside security bugs, is Linus’ law still invalid? Any reference to any material on this?
Ask HN: Examples of good technical writing?
141–145 of 145 posts
Re: Ask HN: Examples of good technical writing?
#142James Gleick‘s “Chaos”[0] (history of chaos theory) and “The Information”[1] (history of information theory) are so beautifully and artfully written you might forget they’re technical. As close as (history of) science writing comes to poetry. A lot drier but top marks for clarity: “Linear Algebra Done Right” by Axler.[2] It got me through both undergraduate and PhD math degrees. When something was confusing in a lect…
Re: Ask HN: Examples of good technical writing?
#143It’s a stretch but I’d say a lot of modern analytical philosophy could be considered “technical” in the sense that the convention is to articulate ideas and arguments as clearly and precisely as possible. My recommendations would be Hilary Putnam, Nelson Goodman, and W.V.O Quine. A paper I’m currently reading, which was seminal in phenomenology, is “ The Phenomenology of Cognition: Or What Is It Like to Think That P?…
Flippin' eck, I've just tried reading the opening sentence: > A number of philosophers endorse, without argument, the view that there’s something it’s like consciously to think that p, which is distinct from what it’s like consciously to think that q. I've re-read it umpteen times and by brain still refuses to parse it. This is not, IMHO, articulating anything clearly or precisely.
For what it's worth, in the expression "to think that p", "p" is meant to designate any arbitrary proposition; e.g., if p is the proposition "it is raining", then "to think that p" expands to "to think that it is raining". (Likewise q is some other arbitrary proposition.) "There's something it's like to X" is a conventional way of saying that (under normal circumstances) X causes or corresponds with a conscious experience. In the quoted sentence "consciously" is a little superfluous, but the paper is dealing with phenomenology (the study of first person conscious experience), so I'm assuming the author added it for emphasis.
It's a pretty technical paper and there's a lot of terminology and assumptions of background knowledge. I definitely find myself reading sentences over and over, but I tend to assume that those issues are more the result of my lack of understanding than of clarity of writing.
Re: Ask HN: Examples of good technical writing?
#144Re: Ask HN: Examples of good technical writing?
#145Code: The Hidden Language of Computer Hardware and Software by Charles Petzold is an excellent work that very clearly guides the reader through the components and steps that lead to the sophisticated computer systems we have nowadays. Each step is explained with no logical leaps and could be followed by a young child. Improving almost anything by George Box blew my mind. As children and even as university students we…