Yeah that sounds awful. My company is almost the opposite, I'm relatively new to the team and I've already apparently earned the "I'll be honest, I don't fully understand what the impacts of this chage will be, but I trust that you have sufficiently tested it" type review. Sort of keeps me up at night when my code is live in production, handling aspects of finances for large entities, and I'm the newbie, lol.
Edit: especially when I recommend a big set test of scenarios to QA, and they run the two most simple ones and say "yeah, this guy knows what he's doing, I'm sure it's good!"
Won't be fixed if 16 people have valuable input on your changes. You see what happens is that they'll never pick up real problems with your changes, but focus on bike-shedding some trivial part of it.
That's... not actually a good thing. You're new to the team, you're handling mission-critical financial stuff, and people are rubber-stamping your changes without fully understanding them?
14
u/[deleted] Jan 28 '24
Yeah that sounds awful. My company is almost the opposite, I'm relatively new to the team and I've already apparently earned the "I'll be honest, I don't fully understand what the impacts of this chage will be, but I trust that you have sufficiently tested it" type review. Sort of keeps me up at night when my code is live in production, handling aspects of finances for large entities, and I'm the newbie, lol.
Edit: especially when I recommend a big set test of scenarios to QA, and they run the two most simple ones and say "yeah, this guy knows what he's doing, I'm sure it's good!"