I've been having two thoughts lately about my blog. First, I need to change its focus so I write more; Second, I need to write more.
Well this post will be the kick-off to the focus changing. I don't write on an SDK these days so the title is a bit of a misnomer. Also, I used to work with an editor who inspired me to write in my blog, Dave Baldwin. Dave also kicked me in the pants recently by saying, "Hey, dude. You ain't writing in your blog. Write something." Well, he said something like that. More polite.
I've had this thought in my mind for awhile. At my employer, we celebrate the ability to "deal with ambiguity." While thinking about this over my second cup of coffee, I decided that there is really only one way to deal with ambiguity: reduce ambiguity. That is, have less of it. Unvague. Increase clarity.
If you wanted to improve your ability to deal with it, what would that look like? I'm going to hit you with a stick in the dark. It will hurt so you should find a way to not get hit by the stick. It will be at random intervals and from random places. You won't know when or how I will it you. In a word, it will be ambiguous. Now, deal with it.
I'm sorry but I don't see any way that you can improve on your dealing with it. You can complain less about it. You can steel yourself for the inevitable pain, but that's not exactly dealing with it.
If you had to ship something, but no one tells you the deadline. The deadline is ambiguous. I don't see dealing with that as a good solution. Why don't we hide all the mailboxes while we're at it. You can mail stuff; it will just be harder.
Ah, but the ability to deal with ambiguity got you this cushy job, a huge paycheck, and the undying devotion of your peeps, the customers. No? Well at the very least, if you happen to be in an ambiguity-laden position here's hoping it is doing something that you really love. That *would* make it worthwhile, no?
Oh, did I mention that I still think the title should be something music related like 'Blasts from Tuba Boy'. ;o)
As a Microsoft contractor, I have been asked the "How do you deal with ambiguity?" question in job interviews quite a few times. It is a “process” question in which there is no correct answer, but it enables the interviewer to size me up in some way. What that way is, I have no idea. It depends on the hiring manager. I don’t think the “Reduce ambiguity” answer is going to do anything more than jump-start the next question, “How are you going to do that?” As questions go, I would prefer to answer the first question rather than the second. At least "How do you deal with ambiguity?" enables me to portray myself as a wise old veteran of the technical writing business who has solved myriad problems over a long and (I might add!) highly successful career. Of course, as an answer, it is total B.S. Even so, that answer seems to work every time. If I get the job, it is all good.
Next question?
As a Microsoft contractor, I have been asked the "How do you deal with ambiguity?" question in job interviews quite a few times. It is a “process” question in which there is no correct answer, but it enables the interviewer to size me up in some way. What that way is, I have no idea. It depends on the hiring manager. I don’t think the “Reduce ambiguity” answer is going to do anything more than jump-start the next question, “How are you going to do that?” As questions go, I would prefer to answer the first question rather than the second. At least "How do you deal with ambiguity?" enables me to portray myself as a wise, old veteran of the technical writing business who has solved myriad problems over a long and (I might add!) highly successful career. Of course, as an answer, it is total B.S. Even so, that answer seems to work every time. If I get the job, it is all good.