Archive

Category Archives for "Russ White"

Intellectual virtue and the engineer

Plane_crash_into_Hudson_River_(crop)On the 19th of January in 2009, Captain “Sully” Sullenberger glided an Airbus A320 into the Hudson River just after takeoff from LaGuardia airport in New York City. Both engines failed due to multiple bird strikes, so the ditching was undertaken with no power, in a highly populated area. Captain Sullenberger could have attempted to land on one of several large highways, but all of these tend to have heavy traffic patterns; he could not make it to any airport with the power he had remaining, so he ditched the plane in the river. Out of the 155 passengers on board, only one needed overnight hospitalization.

There are a number of interesting things about this story, but there is one crucial point that applies directly to life at large, and engineering in detail. Here’s a simple question that exposes the issue at hand—

Do you think the Captain had time to read the manual while the plane was gliding along in the air after losing both engines? Or do you think he just knew what to do?

Way back in the mists of time, a man named Aristotle struggled over the concept of ethics. Not only was he trying to Continue reading

QOTW: Genius

“Genius is long patience,” but it must be organized and intelligent patience. One does not need extraordinary gifts to carry some work through; average superiority suffices; the rest depends on energy and wise application of energy. It is as with a conscientious workman, careful and steady…
Sertillanges, The Intellectual Life

LinkedInTwitterGoogle+FacebookPinterest

The post QOTW: Genius appeared first on 'net work.

Reaction: Interoperate or Die

the-point-fred-wolf-1Ethan has an excellent post up on Interoperate or Die. Herewith, a few thoughts in response.

From my perspective, the importance of open standards in the world of network engineering can hardly be overstated. As networks become more complicated (or complex, depending on what word you want to use), having consistent interfaces will become increasingly important. Think of the old IP model — every transport runs on top of IP, and IP runs on top of every physical/link layer. Using IP as a “choke point” built a “wasp waist,” a single API everyone on both sides of the narrow point in the protocol layer could talk to.

in recent years, we’ve forgotten the wasp waist. We’ve built everything over HTTP, and everything over Ethernet over IP, and everything over GRE over IP, and… The entire stack, above IP, is a hornet’s nest of convoluted caverns and side halls pointing, apparently, everywhere at once (like the guy from the forest in The Point, above).

If you think of IP as an API (which is really what it is), the point is to have a single layer API between any two interacting systems. This creates a clean interaction surface that helps you to Continue reading

Out with the old: Make removing old technology part of your culture

Friday afternoon, late, and the new system is finally up. Users are logged in, getting their work done, and you’ve just received an email from the CTO (your boss’ boss’ boss’ boss, probably), saying what a good job the team did in getting things up and running so quickly. For once, in fact, the system went in perfectly. There was no close to team breakups over which technology or vendor to use; there were very few unexpected items that crept into the budget, the delays were minimal, and you even learned a couple of new skills to top it all off.

Wonderful, right? The perfect unicorn project.

But before you break open that bottle of bubbly (or whatever cold beverage is your choice), or maybe pop up a bowl of popcorn and sit down to a long deserved break binge watching the shows you missed pulling this thing together, you need to ask one more question:

Did you strip and sand first? Or did you just paint right on top?

Or don’t you remember the time you tried to paint that old trailer that had been sitting in your back yard for ages? Sure, it was covered in rust, dirt, Continue reading