A team effort, reluctantly
I’m not much of a team player. Too hard getting all the ducks in a row. However, from time to time, in a crunch, I will relent and call upon others who are wearing the same (two sizes too small) jersey, to “get the job done”. This morning, I returned to some emails about a particular order for “power cords”. Not going anywhere fast, this one. I decided to share my bewilderment with the rest of the group (hence the team imagery). Together, we concluded that we were right and the person at the other end of the dialog was wrong. Then, I dug into the spare power cord box and we sent off the particular type that was needed. If you have to hold an opinion, hold the right one.
This afternoon, I learned that one of our VC codecs has joined a team of its own – a botnet team. Not impossible; it’s a computer, attached to the Internet. But who is going to fix the problem. Once again, conference time (no video required) with others in our group, and after several phone calls the conclusion was reached. Not our problem. A solution will be found, but with the assistance of the reseller. We will not try to reverse engineer the firmware of our codec.
A new iPhone to hand off (the slippery one I mentioned earlier this week). Part of my setup requires adding the email profile of the end user. And, it wouldn’t work. Once again, call in the reinforcements. No joy, until one of the techs recalled the password (of the user standing in our midst). All the ducks, etc. And a nagging question: What to do with a user that doesn’t realize that a password must be typed correctly for the magic to happen.
