erupted on January 11th 2006 175 miles from Anchorage.
Their website has received more than 200 million hits from visitors who want to view the information streamed live from over 30 cameras and recording devices set up in its vicinity.
Under a section titled
Safe Driving While in an Earthquake
"Drivers in California travel in the car approximately 63 million times a day"
I am curious to know how they came up with that number ?
Under the section titled
Emergencies - Dealing with Brake Failures while driving
Sideswipe Objects (attempting to reduce speed)
Sideswiping involves slowing the vehicle by deflecting the car off other objects on the road. No object should ever be hit head-on, nor should objects like curbs be hit, as they could cause the car to over-turn. Guard rails and parked cars would be good objects to sideswipe, as they might gradually slow the vehicle.
err...ok
"The flow-chart is the most thoroughly oversold piece of program documentation. Many programs don't need
flow chart at all; few programs need more than one-page flow chart....."
"The detailed blow-by-blow flow chart is an obsolete nuisance, suitable only for initiating beginners into algorithmic thinking. When introduced by Goldstine and von Neumann the little boxes and their contents served as
a high-level language grouping the inscrutable machine-language statements into clusters of significance. As Iversion early recognized, in a systematic high-level language the clustering is already done, and each box contains a statement. Then the boxes themselves become no more than a tedious and space-hogging exercise in drafting; they might as well be eliminated. Then nothing is left but the arrows. The arrows joining a statement to its successor are redundant; erase them. That leaves only GO TO's. And if one follows good practice and use block structure to minimize GO TO's, there aren't many arrows, but they aid comprehension immensely. One might as well draw them on the listing and eliminate the flow chart altogether..."