2 ms·
It is certainly possible to achieve these things by the methods you name. I'm sure some good employees do. But it is also perfectly possible to achieve good pe
by danaris 6y ago
It is certainly possible to achieve these things by the methods you name. I'm sure some good employees do.
But it is also perfectly possible to achieve good perception, strong connections, lots of face time, and ability to handle office issues, while also being really bad at your actual job, and without any of the positives you mention (except for the fairly bland "easy to get along with").
The real problem, of course, is that what office politics optimize for is extraversion over performance, so anyone who's introverted (which a disproportionate number of programmers still are) is going to come in at a disadvantage.
And, um...if you're writing the code that's required of you, by the people who require it, and you're writing it well and in a timely fashion, it doesn't matter if you brag about it to everyone around, it's plenty useful to the company. I don't know where you've worked where the primary work you've done has been code that you've come up with on your own, which you've then had to "sell" to your own bosses and coworkers, but that's definitely not the norm.
- asciident 6y agoI think you're projecting your idea of "person who is bad at their job but good at selling / office politics" into what I wrote. Of course you need to be good at your job, but how do you even know what's useful to the company if people don't find it easy to discuss problems with you? How do you communicate how long something will take if there is a dependency on another team? Unless you're just writing rote plumbing code, these are all things you need to know.
- danaris 6y agoWell, first of all, I've seen people firsthand who get promotions and raises due to schmoozing who are demonstrably bad at their jobs (in and out of tech). I didn't think the existence of such people was in question. Second of all, you seem to be looking at things in very black and white terms. Of course you need to be able to communicate project requirements and dependencies and whatnot, both within and between teams. That's nowhere near the same thing as "networking" or "making connections" in the commonly-understood sense, which is much more about going over to have a chat and a laugh with Steve or Patty down the hall...or, to take it a step further, going out for a game of golf and running into the CTO there, and just happening to have a chat about your upcoming review. So, in short: yes, of course "being good at your job" requires communication and people skills, as well as (in our case) coding skills. But there are many places where the skills required to advance—both financially and in your career—are exclusively the people skills, regardless of the fact that the skills that are primarily relevant to job performance are the coding skills. This creates perverse incentives, results in unqualified people getting managerial positions, and massively disadvantages those who genuinely care more about doing a good job than "selling themselves"—especially introverted people—in the workplace.