Trouble with this is you need to explain why you touched a bit of code unrelated to the current Jira ticket.
And if you have to explain that alot then you become a problem to the team lead.
If I had to justify myself every time I took the basic initiative of fixing errant, problematic or poorly performing code just because it wasn’t ordained and blessed for me specifically I am out the door SO fucking fast…
Happy to have discussions and elucidate to others the change, and make whatever documentation necessary available, but if some leader somewhere things I’m a “problem” for merely having done the work…okay, let me solve that problem too: bye.
That’s an environment with serious trust issues manifesting as micro-management and I’ve got a severe case of post-micromanagement-stress-syndrome.
They don’t have to “notice” it. They don’t even have to see it.
Do you have an access badge to get into your company campus/building/suite?
My last job started tracking access badge activity to monitor and enforce RTTO compliance.
Found it funny to get nagged about not hitting the required minimum number by a boss who lived four states away.
Laughed all the way out the door and into a new company whose policy is “if you wanna wfh, then wfh. If you want to come to the office, be our guest.”