Since you’re Gen Z, it sounds like you may also be relatively new in your career, and this strikes me as a timeless problem of experience.

Young people come in with a fresh set of eyes and say “why don’t we just do X?” Then more experienced people know all the unfortunate reasons why it’s not that easy. Like in your example, it’s arguably a better policy to just run every patch that gets released, even if it’s not applicable. The alternative is to spend some amount of man hours evaluating whether each patch is needed or not; and occasionally dealing with the consequences of somebody mis-identifying a critical patch and deciding not to install it. The cost from that is greater than the cost of occasionally having to clean up a bad patch that breaks something.

I do agree that Gen Z seems to feel a greater sense of unfairness when they (as less experienced employees) get stuck doing more of the grunt work in a situation like that. I’ve had several issues with Gen Zers at my company feeling like they’re supposed to be working on bigger and better things than the entry level tasks we’re giving them, and becoming disgruntled about it.

Not really sure what to do to manage around that part of the problem though. With millennials in that position, I had reasonable success by giving them a bigger project, then reviewing it thoroughly and helping them see the areas they needed to improve in. The Gen Z’s I’ve tried that tactic with have then felt like they were being “picked on” any time they got critical feedback. I haven’t had it happen enough to know if that’s a generational thing or just those specific people though.