How geeks think

So, the elevator in the building where I work sucks - when you get in on the ground floor and hit the button for your floor, it takes about 30 seconds before the elevator doors shut. I know that's not a long time, but it feels like an eternity when you're standing there waiting for the doors to close.
So, I noticed that when one elevator car is in this process, and another elevator car brings people to the ground floor, the second elevator car will close its doors almost immediately after the folks get out. So, I figured, the programming for the elevator designates the first car as "waiting for folks to get on", and the other cars as "free to roam". This situation actually comes up quite often.
So, after noticing that, the next time the opportunity pops up I jump into the second elevator car right after everyone gets out. Someone else jumps in with me. We both hit our buttons as the doors are closing, and the elevator immediately resets - the doors open, all the lit buttons become un-lit, and then 30 seconds later we're off. Definitely not an improvement.
So, the next time it comes up and I'm alone, I jump in at the last second, wait until the doors close and the elevator starts to move, then hit my button. Success!

I know it sounds stupid to be going through all this trouble just to figure out how to save 30 seconds once in a while, but it's more the challenge of it and the idea of "is there a way to make this experience better / faster / more efficient?". That's how I think all the time, about everything. My wife, thankfully, finds it quirky and charming, but give her a few more years with me and she may change her mind about that.
For you non-geeky people, this is how geeks think about everything - I don't know if it's on account of my work or if this trait makes me suited for tech work, but it seems to be a trait common to most techies. If you can't stand someone like that, don't get involved with a techie...