Earlier quoted context omitted.
When has employment politics ever meant "leveling up in soft skills"? Employment politics has always meant: brown nosing, throwing vulnerable people under the bus, posturing, taking credit for other people's contributions, blaming other people for your failures, and on and on. Or to use the language of TFA, "iNfLUeNcE".
If that’s all you see, you probably need to level up your soft skills. Certainly the things you’re talking about are real, and particularly severe in some environments, but there’s a lot of room to improve your influence without engaging in any of that.
Don't avoid workplace politics
71–80 of 332 posts
Re: Don't avoid workplace politics
#72I clicked hoping to find am argument to the engineering community at large to recognize the political aspects of our work.
Although I guess the basic argument still applies.
Re: Don't avoid workplace politics
#73Re: Don't avoid workplace politics
#74> Hence it is evident that the state is a creation of nature, and that man is by nature a political animal. And he who by nature and not by mere accident is without a state, is either above humanity, or below it; he is the ‘Tribeless, lawless, hearthless one,’ whom Homera denounces — the outcast who is a lover of war; he may be compared to a bird which flies alone. Sure, Aristotle wasn't talking about corporations, b…
- more focus of personal responsibility for my own actions, I do not belive that uknown electorate solve my problems
- open mind for those, who have different political view, I no longer see enemies and it gives mindset to have less biased conversations on various topics
- more time to education about alternative topics, creativity, building, care about family, etc.
Re: Don't avoid workplace politics
#75"Think about the last time a terrible technical decision got pushed through at your company. Maybe it was adopting some overcomplicated architecture, or choosing a vendor that everyone knew was wrong, or killing a project that was actually working. I bet if you dig into what happened, you’ll find it wasn’t because the decision-makers were stupid. It’s because the people with the right information weren’t in the room.…
1) Since around 2008 I’ve had 8 jobs after staying at my second job for nine years. Whether I was laid off or chose to get another job because of salary compression and inversion, being able to get a job quickly - and it’s never taken me more than a month even in 2023 and last year - was partially because at now 51, I have made damn sure I stay up to date with real world use of the “latest hotness”.
2) see #1
3) if you are a VC backed company, your shining light is not “make a good product”. It’s “the exit” and shortly afterwards a blog post about “our amazing journey” where they announce the product is going to be shut down.
The goal of politics in the office is not to do “the right thing”. It’s to stay in alignment with the people who control your paycheck and to make sure you can keep exchanging money for labor when time comes to her another job.
Re: Don't avoid workplace politics
#76"Think about the last time a terrible technical decision got pushed through at your company. Maybe it was adopting some overcomplicated architecture, or choosing a vendor that everyone knew was wrong, or killing a project that was actually working. I bet if you dig into what happened, you’ll find it wasn’t because the decision-makers were stupid. It’s because the people with the right information weren’t in the room.…
I think the article is arguing that if you build the relationship, you can involve yourself into these conversations early enough to direct them the way that your idea would go. In your cases, for example: 1. Recognizing early enough that this Hot New Thing incentive is here and figuring out how your Good New Thing can live with the Hot New Thing 2. Helping show the Old Bad Thing is unworkable for your Good New Thing…
Re: Don't avoid workplace politics
#77Earlier quoted context omitted.
When has employment politics ever meant "leveling up in soft skills"? Employment politics has always meant: brown nosing, throwing vulnerable people under the bus, posturing, taking credit for other people's contributions, blaming other people for your failures, and on and on. Or to use the language of TFA, "iNfLUeNcE".
This is frankly a very childish and Reddit-level take on the issue.
Re: Don't avoid workplace politics
#78When Jeff Hodges gave a presentation of his "Notes on Distributed Systems for Youngbloods"[1] at Lookout Mobile Security back in like 2014 or 2015, he did this really interesting aside at the end that changed my perception of my job, and it was basically this. You don't get to avoid "politics" in software, because building is collaborative, and all collaboration is political. You'll only hurt yourself by avoiding lev…
I used to work for a software company that literally had "no politics" as part of its DNA. It was in the company handbook, it was in our values, people would say it when they talked about what it was like to work at the company. Hell, whilst I can't recall any specific instances, I guarantee that I said it and probably many times[0]. But, of course, it was never true. It might have felt true - certainly superficially…
Anything that violates those core precepts are rejected out of hand, and often times for things that would support the companies stated principles.
I have worked 20+ jobs in my life, and either petty bullshit or greed rules the top of the heap in all but the most particular circumstances. I cant even remember how many meetings I have setup with CEO's to hand feed them information and cheer them on like a toddler so they can make the obviously correct decision.
Re: Don't avoid workplace politics
#79Re: Don't avoid workplace politics
#80"Think about the last time a terrible technical decision got pushed through at your company. Maybe it was adopting some overcomplicated architecture, or choosing a vendor that everyone knew was wrong, or killing a project that was actually working. I bet if you dig into what happened, you’ll find it wasn’t because the decision-makers were stupid. It’s because the people with the right information weren’t in the room.…
Another point worth bringing up is that sometimes, that stuff doesn't matter. I see so many engineers get hopelessly invested in technical debates that are, honestly, just silly: it's often better for the company to get something barely-good-enough done quickly than to flesh out the "optimal" design over the course of weeks or months, and over the dead bodies of people who have a different opinion about vi-versus-emacs.
And even if you accumulate tech debt, it is sometimes a wise decision to pay it back later, when you (hopefully) have more money and time.
So, I'd add "pick your battles wisely" to the list of tips.