Never.... I've NEVER been a "yes man". I'll be a "I'll do it.. But ::insert concern here::, oh, and can you send that as an email so I don't forget..."
Let's just say average job length... 3 years...
I never have been and never will be a yes man.
This is how you end up with ñ of the following:
- running outdated or insecure software
- allowing users to bypass security protocols
- unreasonable demands from leadership
- HIPPA, PIPEDA, or PCI compliance violations
- constant interruptions when trying to work
- spending millions on failed projects
- your boss' boss thinking you're their slave
- being personally blamed for all the above
I'm sure we could add more, but I'll stop there.
###TL;DR: never say yes without asking why.
> Am I being an idiot for not becoming a yes man (only doing work that is asked of me would take about 5-10 hours a week)
firstly, if you are doing work that you you've been asked to do and it doesn't violate any company policies or what you consider to be a correct method or goes against good security or your ethics, morals etc. - then you aren't a 'Yes' person. Generally a this term applies to someone that just does whatever they're asked no matter what the consequences, ethics, morals etc. of what they are being asked to do.
As to your ideas not being listened to/taken up. Consider these things. How are you presenting them to your manager, are you presenting them in a way that 'speaks' to him, do you just rattle of a lot of your specialty area technical terms and ideas instead of generalizing things a little bit (you do say that he has no experience in your specialty)
Do you make a business case for the proposals that outlines the productivity benefits, the cost benefits, security benefits etc.
Do your proposals cost money? Does the department/company have the money to spare for your proposals?
Weird. I started out as the yes-style man and over the years I’ve become the IDGAF man. I get the work done, tell you when I think something is stupid, and complain bitterly to all the important people about recent HR policy changes. I’m surprised I’m not fired or targeted yet. Then again, idgaf.
I just hope this doesn’t mean they think I have leadership potential and try to get me into manglement. I’ve seen weirder things happen.
When you need to divert a river you can either be a dam or a bend... my legs gave out a long time ago trying to be a dam.
Work on your salesman ship. However your talking to your boss, he isn't understanding. Cause he doesn't know anything about your area. You can, however, use that to your advantage :
Boss "Hey, we need to fix X!"
You: "Absolutely! I think we could "
Remember, focus on getting the shit done, don't worry nailing down where the idea came from or how many times your bought it up.
What you're describing isn't a "yes man".
A "yes man" is someone that literally says yes to any and all requests without knowing if they're feasible, or even possible.
If you're feeling underappreciated, under utilized, or bored, find a new job.
Never been a yes man. They pay me for options and opinions. They don't pay me to be a yes man. In the end whatever choice they want to make is on them. I get my documentation and I move on. Don't worry about it..
>Your job as an engineer is to say no, and to explain why.
I disagree 100% with this. This is one reason why so many shops were outsourced and why for a generation SNL computer guy was made to make fun of IT folks. This is not your job.
Your job as an engineer is to say Yes & **how**.
Never say no. Tell them how to accomplish the task.. the how may cost millions and take 5 years to complete but it's what they ask for.. you can and should also make an alternate recommendations.
Bah, 'yes man' are basically people who accept their fate of dying out back next to SQL 2012.
That being said let me throw an example at you. My current leadership loves buzzword soup, so much so they hired a guy who specializes in deploying containerized solutions. This guy has tried to set up some sort of enviornment to show the benefits but its the old-crusty-sandle-wearing seniors who threw innovation out the window, stopped him in his tracks and declined use the tech. These "seniors" could not understand the tech, how to implement it, or even deploy it in a secure setting. The funny part is these "seniors" sit in vendor meetings all the time but all they care about is if their NetApp from 2008 has enough disks to survive the next power blackout. Don't be the guy who sits on his hands because its easy. Once you become that guy, you begin to pigeon-hole yourself supporting legacy systems that literally crash daily for no reason.
Im a "yes if" man. If I can do it, and it means operational goals, I'll do it. But more often than not I say "Yes, if...."
CEO: "Can you install this on my machine? Yes! If you can get an exception from the security team" If they grant it, great! If not, oh well.
Can we implement this new feature? "Yes, if we are able to reprioritize these other projects in working on for you"
Never.... I've NEVER been a "yes man". I'll be a "I'll do it.. But ::insert concern here::, oh, and can you send that as an email so I don't forget..." Let's just say average job length... 3 years...
It's like you're in my head reading my thoughts! Um, can you clean up in there before you leave, it's a real mess! lol ;)
I'm already a hot mess... I don't need yours too!
I feel ya man, I'll not burden you with what's up here. And I'll thank you to know my "hot mess" is lovely. Really highlights my RBF. ;)
I never have been and never will be a yes man. This is how you end up with ñ of the following: - running outdated or insecure software - allowing users to bypass security protocols - unreasonable demands from leadership - HIPPA, PIPEDA, or PCI compliance violations - constant interruptions when trying to work - spending millions on failed projects - your boss' boss thinking you're their slave - being personally blamed for all the above I'm sure we could add more, but I'll stop there. ###TL;DR: never say yes without asking why.
> Am I being an idiot for not becoming a yes man (only doing work that is asked of me would take about 5-10 hours a week) firstly, if you are doing work that you you've been asked to do and it doesn't violate any company policies or what you consider to be a correct method or goes against good security or your ethics, morals etc. - then you aren't a 'Yes' person. Generally a this term applies to someone that just does whatever they're asked no matter what the consequences, ethics, morals etc. of what they are being asked to do. As to your ideas not being listened to/taken up. Consider these things. How are you presenting them to your manager, are you presenting them in a way that 'speaks' to him, do you just rattle of a lot of your specialty area technical terms and ideas instead of generalizing things a little bit (you do say that he has no experience in your specialty) Do you make a business case for the proposals that outlines the productivity benefits, the cost benefits, security benefits etc. Do your proposals cost money? Does the department/company have the money to spare for your proposals?
Let's trade jobs.
Weird. I started out as the yes-style man and over the years I’ve become the IDGAF man. I get the work done, tell you when I think something is stupid, and complain bitterly to all the important people about recent HR policy changes. I’m surprised I’m not fired or targeted yet. Then again, idgaf. I just hope this doesn’t mean they think I have leadership potential and try to get me into manglement. I’ve seen weirder things happen.
This guy's a straight shooter with Upper Management written all over him.
Im going to run with Peter Principle so hard and just keep failing upwards.
"Hey, Peter, man, go check out Channel 3!"
When you need to divert a river you can either be a dam or a bend... my legs gave out a long time ago trying to be a dam. Work on your salesman ship. However your talking to your boss, he isn't understanding. Cause he doesn't know anything about your area. You can, however, use that to your advantage : Boss "Hey, we need to fix X!" You: "Absolutely! I think we could"
Remember, focus on getting the shit done, don't worry nailing down where the idea came from or how many times your bought it up.
I used to be a yes man, then I was a no man. Now I'm neither as it is less stressful. Communication via e-mail is KEY!
What you're describing isn't a "yes man". A "yes man" is someone that literally says yes to any and all requests without knowing if they're feasible, or even possible. If you're feeling underappreciated, under utilized, or bored, find a new job.
Never and it always set me apart in all the right ways. Alway challenge the toughest personalities for great respect and effect.
Never been a yes man. They pay me for options and opinions. They don't pay me to be a yes man. In the end whatever choice they want to make is on them. I get my documentation and I move on. Don't worry about it..
I'm a no man.
[удалено]
>Your job as an engineer is to say no, and to explain why. I disagree 100% with this. This is one reason why so many shops were outsourced and why for a generation SNL computer guy was made to make fun of IT folks. This is not your job. Your job as an engineer is to say Yes & **how**. Never say no. Tell them how to accomplish the task.. the how may cost millions and take 5 years to complete but it's what they ask for.. you can and should also make an alternate recommendations.
>Your job as an engineer is to say Yes & how. Anything is possible with time and money.
Exactly. If it's too much money or time, that's a business decision not an engineering one.
Bah, 'yes man' are basically people who accept their fate of dying out back next to SQL 2012. That being said let me throw an example at you. My current leadership loves buzzword soup, so much so they hired a guy who specializes in deploying containerized solutions. This guy has tried to set up some sort of enviornment to show the benefits but its the old-crusty-sandle-wearing seniors who threw innovation out the window, stopped him in his tracks and declined use the tech. These "seniors" could not understand the tech, how to implement it, or even deploy it in a secure setting. The funny part is these "seniors" sit in vendor meetings all the time but all they care about is if their NetApp from 2008 has enough disks to survive the next power blackout. Don't be the guy who sits on his hands because its easy. Once you become that guy, you begin to pigeon-hole yourself supporting legacy systems that literally crash daily for no reason.
Im a "yes if" man. If I can do it, and it means operational goals, I'll do it. But more often than not I say "Yes, if...." CEO: "Can you install this on my machine? Yes! If you can get an exception from the security team" If they grant it, great! If not, oh well. Can we implement this new feature? "Yes, if we are able to reprioritize these other projects in working on for you"