Before I hit you with the punchline, let's set everything up.
Read up on Factory Pattern and Dependency Injection, so you will get the punchline. If you are already cool with these techniques, please still read the story, and have a good laugh (I did)!
Okay, here's the situation: parents went away on a week's vacation... Oh wait, not quite.
The real situation was: I had to leave work by a specific time to be home by a specific time, etc. Meanwhile, a coworker calls and asks me if I'm ready to demonstrate that User Interface Prototype hitting the Web Service for that 4 o'clock meeting! I was way ready, but I'm like, "Was this on my Calendar?" and of course it was not on there; Nobody hipped me to that meeting, dude.
Are we there yet?
So, no problem. I will take my rig home and get on VPN access and we are golden.
Except for one thing....
It was so fucking slow on the VPN link to the virtual hosting my remote service that everything was timing out all over the fucking place!
On the upside, I'm glad I was able to test for latency; put timeouts at the top of the list for The Very Next Day.
On the (very) downside, there was only 15 minutes before the start of a 21-person conference call! Out go the "I'm Panicking!" emails to my teammates, as I look into searching for some help with the settings, then determine I'm too panicked to try to deal with it, since the actual timeout would still need to be discovered, and the default 60 seconds was already timing-out.
Are we there now?
We are here now. That's when I remembered the main parts were interface-based, and the class name of the implementation was specified in the configuration file. I simply switched to my debug implementation, with 5 minutes to spare, then sailed through the Demo! You all have one of those, right? Right? Right?
Obviously, the punchline is: It will save your ass in a demo!
No comments:
Post a Comment