[metalforever]

Not to bring in this separate issue, but it can be impossible to navigate this as a technically skilled minority . Some people just don't want to work with you and are not going to work with you unless they can tell you exactly how things should be. In large orgs, you may end up with more than one of these people and they just don't align. If coming up with a design that pleases both of them is possible at all, it ends up being a turd architecturally . Later, because its a turd, people pin blame on you.

[gloryjulio]

When you are blocked by non technical issues, it should be the manager's job to help you clear the roadblocks. If the manager is not doing his job, it's probably time to switch teams or jobs. Tbf haven't seen anything like this yet. There are tons minorities working in tech(myself included)

[metalforever]

This is a separate issue . I’m talking about corralling tech leads from different teams to sign off on an architecture or initiative .

[cudgy]

“If the manager is not doing his job, it's probably time to switch teams or jobs.”

You’ll be switching jobs quite a bit then.

[gloryjulio]

I did change jobs a few times but only for the compensation reasons. My current manager and the past managers are great.

Expectations goes both ways. The companies expect the ICs to ship code, and the ICs can expect to work with competent managers. Pay attention when selecting your team.

[eschneider]

Eh...not so much. There are definitely good managers out there. If you're a strong IC and you have reasonable expectations on what you need for support, it's usually not _that_ hard to identify a good manager when interviewing.

[pg_1234]

Don't think of it as switching jobs a lot.

Think of it as still searching for the right job,

funded by the employers who fail.

[nathants]

many of the truths we cling to, a certain point of view.