the story of project management! for kids.

When I was a young child in the long-ago 1970s, computers were used for something called Data Processing.

Data Processing was done with large machines the size of cars or at least major appliances. In order to make use of it, a customer would bring a problem to a person called a Systems Analyst, who would help the customer understand how Data Processing might help. Then the customer and the Systems Analyst would come up with a plan on how to get the customer’s work done.

The Systems Analyst would bring the customer’s problem into the Data Processing place, and give it to computer programmers. Along with other helpful people called Punch Card Clerks and Computer Operators, the programmers would produce software that helped the customer.

After that, when the customer had more data to be processed, it could be dropped off at the Data Processing place, where the Punch Card Clerks would put data in the software, and the Computer Operators would make sure the machines worked, and then finally the data would be all processed and given back to the customer in a neatly rubber-banded set of printouts on fanfold paper.

In the 1990s it was discovered that everything had changed. A customer could often mash fingers on keys and make the data process right there at the desk, without visiting the Data Processing people. Computers were interactive and talked right back to people, so that dropping off data and picking up printouts wasn’t necessary. And worst of all, customers could talk directly to programmers, it was discovered, and tell them what they wanted, and these new quick interactive computers could give results very fast. The programs were then given to the customers who took them off and used them in their own offices.

So the Punch Card Clerks and the Computer Operators and the nice person at the desk who took the data and gave back the printouts were no longer useful, and they had to go home and stop working at the Data Processing place.

Worst of all, the Systems Analysts lost their jobs too. They were expensive people, since almost all of them were old programmers with experience who had been promoted. They were all fifty years old and not retrainable and didn’t know much about PC computers or other new things. Their entire function had been removed, and suddenly their $60K jobs vanished. So all the System Administrators went home from the empty Data Processing places and sat in their imitation redwood veneered dens in their suburban homes and stared at the wall and drank highballs and then shot themselves in the head with large-caliber handguns.

It turns out that the computer programmers shouldn’t talk to customers after all. They are very optimistic people, for whom everything is almost done all the time. They often refuse to finish things or write down how they work. And they can be mean and weird and not very easy to understand, so that customers become frightened and angry and don’t want to talk to the optimistic people who don’t finish things and snort a lot and wear fedoras indoors. Things like this happened during the 1990s a lot, and many customers didn’t want to have any software if they had to talk to the computer programmers. It was time to bring back Systems Analysts. But they were all dead, because they had shot themselves in the head with large caliber handguns in their imitation redwood veneer dens.

So we have Project Managers now. They are different from Systems Analysts in that they are 30 years old instead of 50, they do not live in imitation redwood paneled dens, and they never did know how to program computers. They drive VW Passats and smoke marijuana and use lots of buzzwords, and they are very good at making customers feel comfortable. Many of them enjoy jam band music and are engaged to people named Chad or Alyssa. They do a lot of the same things the Systems Analysts did, so that the customers get their software but don’t have to talk to the programmers after all, because that was a bad idea. They tell the programmers when things have to be done, figure out on their own how long things will take, and dress much better than the programmers.

And that’s the story of how Project Managers were made.

THE FUTURE LIES AHEAD

One of our internal webservers at the office blew up. It’s an intricate and bizarre hack on a little-used platform, and we’re terrified of it dying because our knowledge of the internals is bad. I was pretty sad about it, and especially so because I had to fix it.

A careful search of the internet found a mailing list thread in which many, many other people had the same problem, all starting after 2006-05-12.

The thread starts here: http://www.mail-archive.com/aolserver@listserv.aol.com/msg09812.html

What turned out to be the problem? All these systems failed at the same time, exactly one billion seconds before the 32-bit Unix epoch ends in 2038. The timeouts set for database threads caused the software to look ahead, gasp in horror and died.

Ladies and gentlemen I’m in a select club of the first victims of the Year 2038 Bug.

My job is weird.

The back of loaf

  1. Silver Spoon Considered Harmful.
  2. Massive Fandom Wank containing the phrase “fandom unity luncheon” somewhere in it. Jesus H. Christ.
  3. Abstain from sex; win fries.
  4. List of unusual deaths (Wikipedia).
  5. I refuse to believe that smllr is a real service. Only John Waters can do Smell-O-Vision anyway.
  6. Doom awaits kitchen gadget lovers: Sur La Table is having a big sale.
  7. How does this violinist make weird subharmonic noises?

Nail the license key to the mast

From a tattered diary page found floating on the mucilaginous ooze of the Salton Sea, June 28 2006:

Day 3 of the Windows XP install. Aft #3 torpedo tube is flooded. Captain refusing to leave his quarters. Lt. Zip has not returned from installing the Com+ Deep Fryer and Full-Service Hapax Legomenon (Disabled) (Automatic) (Brazilian). I know that I shall never see my true love or my dear parents again. A watery grave awaits.

Anchors aweigh

My father served in the U.S. Navy in the Second World War. For most of the war he was in the Pacific, serving as the radio officer and then the exec of a tanker. In general he had a “good” war; no fighting and a meal and a place to sleep.

One day the ship was to anchor in a bay on a Philippine island. My dad was on the bridge. They brought the ship to the appropriate place and the crew on deck dropped anchor, under the instruction of the deck officer, who was a new Lieutenant JG.

Ship anchors are big, and so are their chains. The anchor had to go down quite a long way in this case because the bay was deep. Everyone stood well clear as first the anchor and then a very thick chain (about two feet thick) roared through the port on the deck while the anchor hurtled toward the bottom.

Then it stuck. A tremendous amount of swearing ensued. With the anchor part way down, the people on the bridge had to keep the ship roughly in place with the engines at almost zero power, while the people on the deck tried to figure out how to unhook the anchor chain. One of the links had flopped crosswise and was being held in place by the anchor’s huge weight. What to do?

The sailors stood around arguing about the best way to handle this; it didn’t happen often. Finally our young lieutenant got tired of all this meat-headed yelling and decided to show his mettle by fixing the thing simply and quickly. He walked up and kicked the stuck chain-link loose.

With a tremendous bang and roar the link popped loose and rushed into the depths, and once again the chain was speeding through the port and they were on their way to anchoring. But where was the Lieutenant? They looked overboard, and around, and up and down. He’d just disappeared!

But my dad, from above, had seen what happened too fast for the sailors to see. The lieutenant had caught his foot in the chain link and been forced at incredible speed and pressure through a small hole on his way to the bottom of the sea.

That’s the story my dad told about safety with tools when I was growing up.