very much so and it’s painted my impression of the people who have SO MUCH more experience and talent than i do; since they’re expected to catch & correct it.
it’s also helped me immensely when i pointed out to them that they missed its implicit insecurity after our peer reviews and i’m know that it pissed some of them off.
it’s more a reflection of my experience and their stereotypical blind spots:
the IT work that i did before becoming a developer has taught me to succeed by placing emphasis on delivering on time and with minimal maintainability to the exclusion of everything else and it verbally sits poorly with the more privileged engineers that i work with; but they do the same thing obliviously nonetheless. like you, they make assumptions based on who they think you are without realizing that they’re the same way.
their insistence that they own all aspects of the peer reviews; plus management’s insistence that we acquiesce to them despite seeing blind spots in the review process; plus their unwillingness to listen to someone who doesn’t fit into the in-group allows for this to happen and i’m only allowed to voice my concerns when prompted to like a soldier in the implicit security example that i shared.
developers are just a screwy as everyone else and the ones that management help to drink their own bathwater is creating a world where new developers will have to be likewise privileged to even be allowed in, in the future; i know that the ivory tower developers believe that this is a good thing, but this disconnect with reality is fueling the socioeconomic gaps that let people like trump win elections and ruin things for everyone.
very much so and it’s painted my impression of the people who have SO MUCH more experience and talent than i do; since they’re expected to catch & correct it.
it’s also helped me immensely when i pointed out to them that they missed its implicit insecurity after our peer reviews and i’m know that it pissed some of them off.
Reviewers are not infallible and are largely focused on the meat of the MR rather than every single detail.
It reflects much more poorly on you than it does on them.
it’s more a reflection of my experience and their stereotypical blind spots:
the IT work that i did before becoming a developer has taught me to succeed by placing emphasis on delivering on time and with minimal maintainability to the exclusion of everything else and it verbally sits poorly with the more privileged engineers that i work with; but they do the same thing obliviously nonetheless. like you, they make assumptions based on who they think you are without realizing that they’re the same way.
their insistence that they own all aspects of the peer reviews; plus management’s insistence that we acquiesce to them despite seeing blind spots in the review process; plus their unwillingness to listen to someone who doesn’t fit into the in-group allows for this to happen and i’m only allowed to voice my concerns when prompted to like a soldier in the implicit security example that i shared.
developers are just a screwy as everyone else and the ones that management help to drink their own bathwater is creating a world where new developers will have to be likewise privileged to even be allowed in, in the future; i know that the ivory tower developers believe that this is a good thing, but this disconnect with reality is fueling the socioeconomic gaps that let people like trump win elections and ruin things for everyone.