inb4 they wait until his last day then roll back the changes because functional code/unauthorized changes are against company policy and actually they need that bug to slow down the user so they don't click so fast the database crashes.
I am steadfast that I will occasionally take some time and kill off some low hanging fruit. For me, its kind of like a break and lets me clear my head on the bigger issues.
As someone in the dev team for a "business app", we probably know about most or all of them, but they're just not important enough for anyone in management to prioritize them as part of a sprint. It's also possible no one has given us reproducible steps to make them happen, so we just straight up don't know what to fix. Usually the former though.
They usually do yes however it's all about prioritization.
You may have hundreds or thousands or open requests and issues.
With tens of thousands of closed issues that were either not reproducible, not actually problems, or largely indecipherable.
There's usually a feature roadmap which is where most of the development money and time is spent. If it's an older business application then certain bugs might easily take weeks to find, fix, test, validate, go through user acceptance, A/B test, and then deploy. But fixing is expensive work, so if the bug isn't severe it's usually deprioritized next to higher priority work.
Pads, calibers and new discs. That seemed like a lot of money for 17 year old kid. I worked there for a couple of months. I learned a few things, like working on brakes is not for me.
Bro that reminds me when I was in university and I used to tutor fellow students with the goal of getting laid. As soon as I got laid I stopped tutoring. Now unfortunately I'm married and have kids because of that.