Hacker News new | past | comments | ask | show | jobs | submit login

They're really "thick" sentences. By the time you get there, your brain has had to process so much that you go "huh".



There's a great book that attacks dense writing and how to fix it [1]. It is a quick read.

For example the author takes this sentence:

Pelicans may also be vulnerable to direct oiling, but the lack of mortality data despite numerous spills in areas frequented by the species suggests that it practices avoidance.

... and turns it into this:

Pelicans seem to avoid oil spills by avoiding the oil.

[1] "Revising Prose", Richard Lanham. http://www.amazon.com/gp/product/0321441699/ref=pd_lpo_sbs_d...


Not stated in the second sentence is the statement of data supporting the observation, or the fact that pelicans are affected by oil.

It's easy to trim sentences when you take away data.


Maybe a footnote or inline citations would be a good compromise?


This sentence is shorter, but it also contains less information. I would say the 75% reduction in sentence length comes with a 66% reduction in contained information.


Ha, spoken like a true engineer. However, if the point of writing the sentence is not data storage but communication, then a long, convoluted sentence can be less successful than a shorter, more readable one. Maybe I picked a bad example. Here is another one:

Before: Perception is the process of extracting information from stimulation emanating from objects, places, and events in the world around us.

After: Perception extracts information from the outside world.

Yes, the first is more specific and more detailed, but the "outside world" includes things like objects and places and doesn't add much to the gist. The second one is certainly more readable.


"Just the facts, ma'am."

I often see writing (especally from engineers) that is meant to be informative that is overwhelmed with irrelevant information. That is difficult to parse. Sometimes you want to pick out just a few relevant facts and leave out anything that isn't strictly needed so your audience understands the point.

It depends on your audience and you reason for writing what sort of information is needed and what is not needed. Its not an easy skill.


Interesting. I'm curious, do you find the technical content to be the 'thickening agent' or the style?

I work in a related field, and am vaguely familiar with both the general makeup of this type of rocket and this accident in general. I also tend to write longer, more complex sentences.

I did not find it to be particularly 'thick', and I'm curious whether it's because I'm more familiar with the technical details and so avoided the glossy-eyed stare from that aspect or from the fact that a few dozen words in a sentence doesn't faze me.

The former would mean this shouldn't bother anyone practiced in the arts of spaceflight (such as the VP of engineering), but the latter would have been a problem.

Edit: stupid homophones.


Both. But the problem is not the thickness per se, it's that the lede is buried beneath the technical specifications. The "thickness" compounds the problem.

"we stand in jeopardy of losing a flight along with all the launch pad facilities" should be in the first sentence of the whole letter, not the final one.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: