The World’s Leading Microsoft .NET Magazine
   
 
The .NET Addict's Blog

My Top Tags

                                                           

My RSS Feeds








I heart FeedBurner

Latest Diggs - Programming

Computers Blogs - Blog Top Sites

Site Hits

Total: 2,817,121
since: 19 Jan 2005

Why programmers aren't the most efficient trip planners

posted Fri 25 Jan 08

Earlier today, I had a pretty typical experience. I picked something up and was heading toward the kitchen with it. Along my way, there were several other items that all needed to go there. I went straight to the kitchen, then came back and made 4 subsequent trips to pick up all the remaining items that needed to go into the kitchen.

See, here's the problem. The instinct to simply get something to work first, and then refactor it to make it more optimal later is so ingrained in me, that I pretty much do that in life too. So here's how this works:

My wife's trip optimization:

  • Decide that she needs to go to the kitchen
  • Use Terminator T-1000-like optical scanning techniques to locate, identify, and prioritize all kitchen-bound items between her and the kitchen.
  • Mentally perform derivitive calculus to determine the smallest rate of angle change possible in order to obtain all items with minimal wasted movement
  • Go to the kitchen with 300 items piled to the ceiling
  • Priorize the items in the pile by the desired destination within the kitchen
  • Unload flawlessly
  • Wonder why the hell a man can't do this...

My trip optimization:

  • Locate the kitchen
  • Go to the kitchen
  • Forget that there was something I was supposed to bring
  • Go back for said item
  • Go back to kitchen.
  • Repeat single-item fetch and return process until all 300 items are in the kitchen. This takes 300 trips.
  • Decide that there might be an opportunity for refactoring
  • Refactor one step in the system to be more efficient, resulting in 298 trips the next time.
  • Repeat until I'm down to 1 trip, which causes me to make 300 factorial trips
  • Wonder why the hell I can't do this right the first time...

Now I realize that my mind is far more scatterbrained than most, so my situation might be a little extreme (and I'm exaggerating because I think it's funny), but I have noticed a correlation between minds that are trained to break complex tasks into small ones (programmers) and minds that can take a hojillion little steps and turn it into a single trip (wives) and how efficiently (or inefficiently) those people go through their daily lives.

Is this something that happens to other folks, or am I really just completely hopeless and alone in my absentminded professorness?

tags:  

links: digg this    del.icio.us    technorati    reddit




1. Martin Pilkington left...
Sat 26 Jan 08 7:01 am :: http://www.mcubedsw.com

I'm not sure it may be that programmers are more analytical, as that men are, and so make better programmers. I've just been reading this article on the BBC: http://news.bbc.co.uk/1/hi/business/7209353.stm . It pretty much sums up what you are saying, that women think further ahead while men focus on a specific task. It makes me wonder if, while men would make better programmers, being more analytical, would women make better software designers/project managers with their long term planning?


2. Kevin Hoffman left...
Sat 26 Jan 08 7:12 am

While there are certainly exceptions (men who aren't analytical, women who are as/more analytical than most men, etc)... I think there might be something to that. I think I did see a study once that showed, demographically, that there was a steady rise in female project managers and other "plan ahead" type jobs. Correlation?


3. Kelly Gates left...
Sun 10 Feb 08 11:55 am

I have to say I am a lot like your wife. Even when I grocery shop I put everything on the conveyor based on how it will go into the bags (I bag my own groceries). It drives me crazy when the cashier holds thing back and messes up my system, I think they do it on purpose.

I am also a programmer. We try to practice Agile Programming at my company. In other words having a program “just good enough” and then make changes later. It's hard for me because I am already looking at the big picture an the possibilities for the future of the program. Many times will even write my code to where the user gets just good enough but the programmer will have an easy time making the upgrades that I know the user will need in the future. Perhaps it is because I am a woman, I have never thought of it that way but I do know that this way of thinking has saved me and others a lot of work in the end.


Tag Related Posts

Why programmers aren't the most efficient trip planners

Sat 26 Jan 08 12:10 A GMT-05
tags:  

The World of Warcraft Epic Mount Trade

Tue 10 Apr 07 7:16 P GMT-05
tags:        

My Little Pony .NET Unleashed 2007

Fri 30 Mar 07 1:59 P GMT-05

WPF Bumper Stickers

Tue 12 Dec 06 7:32 P GMT-05

Web 2.0 - I've had it all wrong!

Mon 30 Oct 06 8:51 P GMT-05
tags:    

I was "greeted" by a fellow New Yorker yesterday

Sat 21 Oct 06 12:21 P GMT-05
tags:    

White and Nerdy - My new Anthem

Fri 06 Oct 06 3:13 P GMT-05
tags:            

How they delivered pizza in colonial times

Mon 11 Sep 06 11:04 P GMT-05
tags:    

Caution: Do Not Sit on Air

Wed 02 Aug 06 12:20 P GMT-05
tags:  

Dan Brown's got competition

Mon 05 Jun 06 3:51 P GMT-05