> If your manager has objections that's evidence it was a bad idea
You're just pushing responsibility for saying "no" onto someone else. I would look at the concept of "ruinous empathy" - sometimes being too facilitative and not giving feedback isn't good for anyone.
I've worked at so many places that have no planning process and no organization. Right now we all put what we're working on into multiple Google docs manually (docs are scoped to different time ranges and teams, and they overlap in scope) and as the team has grown there's issues with the cursor moving around. There's also no follow-through on whether things in the docs get done.
I would pay 6 figures to have someone step up and impose some kind of order on the process.
The point of a microaggression is that it's part of the constant pressure of not being part of the "dominant race". You can't do a microaggression to a white person because there's no hierarchy where you're above them to reassert.
The problem is eventually the cognitive overhead for reviewers gets so big that you end up at a deficit, where you write code too quickly for them to keep up. Small PRs and fast review latency are good for a team all working on the same thing, but I've been at several startups where review latency was several days because everybody was too busy writing their own code. What results is either giant monster PRs or stacked PRs.
Does anybody have a good, comprehensive guide to Keycloak? I looked at it a while back and it seemed like a giant web UI with a million poorly documented knobs, but I keep seeing people who claim to be using it. I've used Auth0, Okta, Dex, and ORY and none of them seemed quite as incomprehensible