Ever wonder why things are screwed up?


While this story does not relate directly to audio, a undeniable example of the importance of a horse's ass and the role of specifications.

STANDARD RAILROAD GAUGE:

US standard railroad gauge (distance between the rails) is 4 feet, 8.5 inches. That's an exceedingly odd number.

Why was that gauge used?

Because that's the way they built them in England, and English expatriates built the US Railroads.

Why did the English build them like that?

Because the first rail lines were built by the same people who built the pre-railroad tramways, and that's the gauge they used.

Why did "they" use that gauge then?

Because the people who built the tramways used the same jigs and tools that they used for building wagons, which used that wheel spacing.

Okay! Why did the wagons have that particular odd wheel spacing?

Well, if they tried to use any other spacing, the wagon wheels would break on some of the old, long distance roads in England, because that's the spacing of the wheel ruts.

So who built those old rutted roads?

Imperial Rome built the first long distance roads in Europe (and England) for their legions. The roads have been used ever since.

And the ruts in the roads?

Roman war chariots formed the initial ruts, which everyone else had to match for fear of destroying their wagon wheels. Since the chariots were made for Imperial Rome, they were all alike in the matter of wheel spacing.

The United States standard railroad gauge of 4 feet, 8.5 inches is derived from the original specifications for an Imperial Roman war chariot. And bureaucracies live forever.

The next time you are handed a specification and wonder what horse's ass came up with it, you may be exactly right, because the Imperial Roman war chariots were made just wide enough to accommodate the back ends of two war horses.

Which leads us up to today, the space age.

When you see a Space Shuttle sitting on its launch pad, there are two big booster rockets attached to the sides of the main fuel tank. These are solid rocket boosters, or SRBs. The SRBs are made by Thiokol at their factory at Utah.

The engineers who designed the SRBs would have preferred to make them a bit fatter, but the SRBs had to be shipped by train from the factory to the launch site.

The railroad line from the factory happens to run through a tunnel in the mountains. The SRBs had to fit through that tunnel.

The tunnel is slightly wider than the railroad track, and the railroad track, as you now know, is about as wide as two horses' behinds.

So, a major Space Shuttle design feature of what is arguably the world's most advanced transportation system was determined over two thousand years
ago by the width of a horse's ass.
128x128Ag insider logo xs@2xalbertporter

Showing 1 response by mceljo

@ben_campbell - Recognizing that this thread has been dead for two decades, I stumbled upon it today and think that I can add to the mind boggling stories.

The place that I work is a very large business.  One of the core databases that we use requires us to create individual jobs that include individual fields to be filled out for a variety of different purposes.  In the past we could make nearly as many changes as we wanted before saving at the risk of losing some work if something unexpected happened.  This program was recently replaced with a new web-based version and the new version runs much slower.  We have actually documented the new version have more latency in it than it took to complete the entire task with the legacy version.  Yesterday, one of my employees documented that using a less efficient workflow actually resulted in a more efficient overall process. Instead of complete the 44 individual changes in sequence which took 11 minutes, she instead closed the working window after each 10 changes which allowed her to complete the task in 7 minutes.  We literally have a program that forces us to hit save after every single change before moving to another cell and also has no cache so you can literally click back and forth all day between two cells and the latency will be the same, yet it somehow clogs itself up if you do to many individual changes all on a row.  Keep in mind that before a recent update the task took 18 minutes and in the legacy version we estimate that it would have taken 3 minutes.  It's a painful time!