|
While they're both round, I will probably prepare differently to catch either one if thrown at me. Wouldn't you? I might stand differently. I might even ponder, "do I need one hand or two?" I'll definitely consider what could happen if I fail to catch the ball and how it might bounce or even break something where it lands. Mindless musings, you say? Maybe. But really? How is this any different from what most network teams deal with? Seriously. Pretend you're the app guy and I'm the network guy. You know what you're going to throw. You've spent countless hours defining it, building it, making sure it makes the business folks happy, and even (I hope) testing it. You are closer to it - and know more about it - than anyone possibly could (or most would ever care to understand, frankly). So - why won't you tell me about it? Really. Because I don't understand. It's not hard. It probably won't take much time. It certainly doesn't steal your thunder. Here's the deal: I'm going to build for a bowling ball - guaranteed. It's safer. But, know this - I won't be as quick and nimble. It'll take two hands. And, the thought of that coming will certainly occupy more of my mind than a golfball might because I don't want to face the risk (and embarrassment not to mention damage) that dropping it might bring. So, I'll be pretty preoccupied. Forget those other things on my task list. It eat more of IT's budget but be incredibly overbuilt when your golf ball comes my way. And, I won't have the time, budget, or option of help you optimize your app or provide additional security help. I spent it all preparing for a bowling ball (and I'm really quite stressed even about the thought of it.) So, you'll have to write that code. And test it. And update and maintain it. You have plenty of time, right? It's not a pretty picture. But, it's all together too common. Just heard about it from someone - again - today. When will IT groups learn that the good from sharing more information far outweighs any fear of bad that comes from sharing it?
|