Originally published on: 12/19/2006 6:22:23 AM
To properly parse this response, you actually need to estimate the duration of each item on the list, total the estimates, tack on about 20% for overrun and factor in the commute. Only when you've run the response through this wrapper method can you actually get the timestamp you were looking for. And, if you were looking for a boolean, you need to then compare your timestamp against the timestamp for dinner and see which is greater.
So, in essence, having a good marriage is like working in a loosely typed language and you've just got to have really good exception handling. Once you've built up a good library of wrapper methods for how your spouse communicates, things can just cruise right along and work smoothly.
Or I guess you can throw an exception to be handled by the divorce() method. But that seems like a pretty bad approach.
When you're 21, sitting at home with one other person watching TV with a laptop on your lap is seriously geeky. Most people that age would thing you should be "out" and "doing something". By the time you're 31, that expectation isn't nearly what it was and more non-geeks are doing pretty much just that.
In other words, I think as many people get older, their behavior tends to drift toward the behavior of geeks as the same thing tends to happen to geeks.
I wonder what frame of reference my wife wishes I saw our relationship in???
And you pretty much just have to guess the sigma value.
I've translated it to Spanish if you don't mind.
BTW: the only way to kill a SleepOnCouch() function is to call FlowersBigTime() function.
CYA!