Re: Off Topic 2011
So it's time for GIGGAS' story corner.
The President of my company tends to do a little dance I like to call "Fishing for the affirmative".
This occurs when he gets an idea that he thinks is amazing, but generally has already been done and isn't a good idea. He then goes to the major decision makers in the company, regardless of the product they work on (or if it's relevant to the product they oversee) and try to get a yes. Predictably, they say no, because his idea is full of ****.
Then, he goes to people that aren't decision makers, and tries to intimidate them into giving a yes, which he will then use against the major players to make this idea happen. Many developers have fallen into this trap.
This happened today. I work on one specific product, one we'll call Product A. The President of the company came down to talk to me and my cubemate about modifying Product Z. As my cubemate came down from Product X, which is supposedly the replacement for Product Z, he knew some things about what he had to say. I have no idea about Product Z or anything that they do technically, so I clammed up.
This led to a 30-minute conversation between the President and my cubemate, where it became obvious that he just wanted a yes. Luckily, my cubemate had fallen into this trap before and was able to not fall in again.
The moral of the story? I gotta get out of where I work.
So it's time for GIGGAS' story corner.
The President of my company tends to do a little dance I like to call "Fishing for the affirmative".
This occurs when he gets an idea that he thinks is amazing, but generally has already been done and isn't a good idea. He then goes to the major decision makers in the company, regardless of the product they work on (or if it's relevant to the product they oversee) and try to get a yes. Predictably, they say no, because his idea is full of ****.
Then, he goes to people that aren't decision makers, and tries to intimidate them into giving a yes, which he will then use against the major players to make this idea happen. Many developers have fallen into this trap.
This happened today. I work on one specific product, one we'll call Product A. The President of the company came down to talk to me and my cubemate about modifying Product Z. As my cubemate came down from Product X, which is supposedly the replacement for Product Z, he knew some things about what he had to say. I have no idea about Product Z or anything that they do technically, so I clammed up.
This led to a 30-minute conversation between the President and my cubemate, where it became obvious that he just wanted a yes. Luckily, my cubemate had fallen into this trap before and was able to not fall in again.
The moral of the story? I gotta get out of where I work.
Comment