February 26th, 2009

jim

random bits

  • Well, sabbatical is basically about a third over, and to show for it I've got ... um ... not much of anything really.  I keep doing all the "other" stuff, and then doing stuff that piques my interest on committees & stuff, which is cool, but ... sigh.
  • As long as we're sighing ... my never-ending war against unread newspapers has suffered another defeat.  The pile today was six months high.  I threw out everything from before January 1st ... which means I didn't read a newspaper from 2008 at all.   I know, I know ... no false guilt, no false guilt ... at least, that's what I keep telling myself.
  • Of course, now my daughter's home sick from school, after being home most of last week with some other bug.  Figures.
  • I really shouldn't just complain here.  But ... that's where I am at the moment. 
  • I wonder what I can concoct for suppertime ...
  • Current Mood
    discontent discontent
professor

A story to remember: the Vasa

I was reminded today, by some reading, of the tale of the Vasa --- and what it has to tell us for today.

What, you don't know the story?  Well, it's pretty simple, really.

Back in the 1600s, King Gustavus Adolphus of Sweden commissioned a new warship to be built.  Kings at that time got to do more than just order ships to be built; they got to design them, too.  So, the king designed the ship.  And, in particular, the latest craze on warships was to have two decks worth of cannons, so he added those to his design.

Problem was, the ship wasn't wide enough underneath the waterline to compensate for all the extra weight (cannons are heavy, if you hadn't realized that), and putting all that weight above the waterline would've led to a terribly high and variable center of gravity, which makes ships, y'know, likely to tip over and sink.  At least, that's what the designers believed.  So, they told the king.  But the king can never be wrong, so the design stayed as it was.

They even beta-tested it, once it was built, by having crewman run from side to side aboard the ship while it was in port.  It started to tip, so they stopped the test.  But the king can't be wrong, so ... the test was simply cancelled.

The ship put to sea with much fanfare ... and promptly sank, about a mile out of port.  The king was furious and ordered an inquest to find out who was responsible.  Attempts to find blame were put everywhere.  But ultimately, the design was shown to be faulty.  But since the king can't be wrong, the official cause of the sinking was "an act of God".

Ever have one of those situations where your boss simply won't listen, and a disaster results?  It's apparently a very old story.

And a story to keep in mind, in case you become king ... er, um, manager, one of those days in the future.



  • Current Mood
    contemplative professorial
cowboy

victory!

Ok, it's a small one.  But I'll take it.

That massive pile of data that I'm supposed to analyze over this sabbatical?  Well, it's not analyzed.  Yet.  But I have now successfully parsed it into a set of data structures in Java, and verified the success by printing the entire data structure out.  Which is the long and tedious part of the project.

Now, I can start thinking about what sorts of calculations I want to do with this data.  Because it's in a nice spiffy format now.

Yay! 

Aside #1: I need a victory userpic ... cowboy guy just doesn't cut it.  How do I search for userpics?  I know there are some communities I could join, but those seem so freaking big ...

Aside #2: it's amazing how good it feels to code.  I spend so much time teaching coding, that I can't remember the last time I wrote a piece of code that was more than 30-40 lines long.
  • Current Mood
    satisfied satisfied