And this is why skilled people can't find a job. Unless you can kiss a*s you won't get hired. This is wrong! If some one agrees with every word you say, this should be a red light. This might means the person don't have a mind of there own. Unless you want to hire a robot ^_^
Anyway you don't have to kiss ass. All you have to do is have a solution to problems and ability to shape ideas not just cut them off. Unless it's nodejs. That can just fuck off.
When I hire people myself I'm looking for people who are opinionated but can back that up with experience and evidence and thought processes which show how the conclusion was reached. I really don't want to hire passive production monkeys.
- Great idea
- Makes total sense
- That's how I would do it
- I agree
And this is not a joke.
I agree. The problem starts when this sort of friction continues after all the decision-making is done and starts manifesting as contrarian positions towards how the project is being conducted, always insisting that their idea was better, and even assuming aspects of sabotage.
It's one thing to determine a path forward, but an entirely different thing to assume a "my way or no way" stance.
me: "ok."
(even though this will cost hundreds of productivity hours - explaining it to new devs and wondering why all your history disappeared again, sigh you shouldn't rebase on a public branch! , gah fuck it)
Yeah, sure, sounds like a great idea.
Not a problem.
Rebase is a tradeoff of handling merge conflicts with achieving a commit history that is far cleaner and audit-friendly.
The point being that some technical choices are not black and white, and people mistake baseless personal opinions with technical truths. There's an awful lot of workable grey areas with tradeoffs.
If a team member insists on pushing his personal opinions as the truth, challenges and opposes each and every proposal that does not match his personal opinion, and drags on personal vendettas in decisions that didn't went their way... I'd say that no matter where their tech skills are, that person is still incompetent and a liability in any team.
You're trying too hard to rationalize away personal problems and your inability and/or unwillingness to address them.
The opposite of disagreeable is not "kissing ass". The opposite of disagreeable, to start off, is not being a total asshole. No one's technical prowess is impressive enough to ignore the fact that they are completely insufferable. A project survives extra weeks or even months, but a team does not survive an eggeegious team member who makes everyone around them miserable.
Take a long hard look at yourself before throwing blanket accusations at anyone and everyone around you.
As the saying goes, "if someone is an asshole, they're an asshole, if everyone is an asshole, you're the asshole"
"I will say yes to absolutely everything you say" is not at all the same thing as "I will do a good job."
There are absolutely far too many workplaces where you are expected to kiss ass to be hired or to progress.
Personally, I know that I would never feel OK working there, so I don't see the point of trying to pretend I'm an ass-kisser in interviews. I actually am an agreeable person, overall; I just want to find a place to work that will be OK working with me, not with some extremely different false face I have to spend a huge amount of energy putting on every day just to get paid there.
I agree, that you are!
>> The opposite of disagreeable is not "kissing ass". The opposite of disagreeable, to start off, is not being a total asshole. No one's technical prowess is impressive enough to ignore the fact that they are completely insufferable. A project survives extra weeks or even months, but a team does not survive an eggeegious team member who makes everyone around them miserable.
Makes total sense. Great idea.
>> Take a long hard look at yourself before throwing blanket accusations at anyone and everyone around you.
That's how I would do it. You should try it.
>> As the saying goes, "if someone is an asshole, they're an asshole, if everyone is an asshole, you're the asshole"
Makes total sense.
@popotamonga, You were right it does work ^_^
I think its you who are trying so hard to rationalize your own personal problems and/or unwillingness to address them. You may need to seek some professional help!
I'm not a kiss ass type and never will be no matter how well you trying to rationalize your thiking. Been a kiss ass is no different from been a slave to your boss or your workplace. If you prefer to kiss ass do so and don't try to impose your way of thinking on others.
>And this is why skilled people can't find a job
Which is a good thing because it makes it affordable for startups to hire skilled people.
If you're looking for technical work and are really getting rejected because of something at the culture-fit level (which is where "agreeableness" falls), I'd say it's less likely that you're insufficiently kiss-ass/agreeable, and more likely that you're being identified as "potential problem teammate" material for other reasons.
To get a job you don’t have to agree to the nth degree with everything that’s said to you. You just have to be a nice more-or-less qualified person who’s enjoyable to be around and communicate with. That’s a foreign concept to many people (not just programmers) so they look for some “trick” like never disagreeing.
It’s even better that this trick makes them feel better about being a miserable wet blanket because they’re putting one over on the interviewers.
If you mention reservations about either, that's going to cost you.
It's brutal.
Here’s a question for you: What are the benefits of being watched all the time?
I understand that from the employee’s perspective they might not like being watched all the time and that it can affect their behavior. It can also prevent them from doing their best work.
That said, there are reasons why an employer would want to watch their employees all the time. If the employee dislikes it enough and thinks they have better options, they can stop working there.
The only reasons an employer has to constantly be watching relate to paranoia or micromanagement, i.e. a lack of trust in the professionalism and competence of their employees. This is abysmal and the employee quitting or not is unrelated, much as how bullying is bad even if technically an employee can quit. Not to mention that quitting is not an optional for everyone, depending on their circumstances.
I think there's a middle path and I think I'd try to apply it interviews, rather than "just" daily life and work, and that's to assume there's something of value where the other party is coming from, and use your creative powers to try to find that value. Make an attempt to understand the other party with an understanding that your thought process may have to play with things it reactively thinks are bad and solve within that framework before either rejecting the bad thing or finding out it's wrong.
Don't blanket accept or reject their mission statement or tech stack, come with a creative curiosity about it.
If people will actively seeking other teams because of a new member’s personality, it’s something you can bet will be looked for look for in an interview.
Another dimension of the "it depends" response to this is seniority.
If you're relatively junior, or will appear relatively junior based on your resume, don't express strong disagreement, but rather eagerness to learn. The team wants you to be someone who can contribute, and help them make progress towards their current goals. You're not there to re-evaluate decisions about their stack based on the glimpses get you get during the interview process.
But if you're quite senior, the team perhaps wants you to help them level up or improve. Agreeing with everything would also suggest you don't have something new to contribute that helps take them beyond the track they're on now. Don't disagree without a good reason, and be able to explain your thinking. Ask questions before you arrive at a position. Understand why the fence is there before you advocate its removal. But insightful, constructive "disagreement" can still be a way to demonstrate the value you'll bring.
bad: I disagree with the way this is done/this is just bad. Lets do X!
good: I see the motivation with the current approach and understand the goals but i wonder if we might be better served by doing X instead. Usually this allows for Y benefits, but I'm open to discussion here.
Add some fluff to ensure nobody gets defensive and articulate your flexibility (even if you don't really have it)
Sometimes the boss has a bad idea, if you're the tech guy it is your responsibility to decide if it has legs or it's a waste of time. Many consultants say yes to anything because even wild-goose chases are billable. But honesty and integrity tend to pay off in the long run, IME.
As somebody who only does technical interviews, I must say, you better cut that crap out before you get to me. Because I just puked a little.
A candidate that is energetic, excited, and passionate about programming. Practice this in front of the mirror. Record yourself.
Why should I hire you if you don't like my mission, my tech stack or my culture when there are clearly a bunch of talented people who do like all of them?
Would it not serve both of us for you to shut up, be grateful for the work while you keep looking for that perfect fit? Or even better, just keep looking and I'll keep looking for someone who genuinely likes the way we do things.
Next time a company tells you about their mission statement, stop them midway, eyes open in awe, and say "That's my mission statement."
Do the same thing when they tell you about their tech stack. Or anything else. I'm not kidding. The last applicant agreed with everything, and you need to agree with everything harder.
Agreeability and disagreeability are two separate skills but the tech industry sees it as a spectrum. They do not hire disagreeable people.