4 ms·
To be fair, I have a lot of time on my hands :). In defense of the OP, they are covering one of the oldest and most well-known engineering history lessons, not
by danso 11y ago
To be fair, I have a lot of time on my hands :). In defense of the OP, they are covering one of the oldest and most well-known engineering history lessons, not a new trend or news event. A lot of history we take as gospel gets summed up in glib paragraphs, so if someone is purporting to explain why something has been wrong for decades, I won't hold it against them if they take more than the usual amount of words to get there.
- maxlybbert 11y agoBut they aren't filling the article with useful facts or details. It's all intellectual popcorn. Mention that something big is coming up, then mention what the main engineer ate for breakfast, then pause to lament the fact that people often skip breakfast, and finally reach your big reveal. Then claim the fact that it rambles is proof of good writing.
- mcnamaratw 11y agoExactly. This particular article isn't providing much depth. It's mostly misdirection followed by a dramatic revelation of the generally-accepted answer. The dominant guess at the failure mode of that bridge has been flutter for a very long time. Anyone else who has gone through the mechanics and disagrees with me on this, please let me know your thinking.