I'm a tester through and through and don't really work with our codebase much outside working on automated tests. But sometimes, not often but more than 0 times a year, I find an issue with a task I'm working on, see the code changes made, and immediately see the problem and the fix is literally just one line change or very simple in some other way. And sometimes the developer who made the change is on vacation or otherwise unavailable.
So I take initiative.
I just go ahead and make the fix and commit to the branch.
And so far 10 times out of 10 that fix resolves the issue without having to wait for someone else to take a look, read task description, read through the code and check the changes, and go through the hassle of switching context from whatever they were working on before to this small insignificant issue.
It's not really "according to process" or anything, but when it comes to software development, I have a strong opinion that sometimes you just have to say "fuck the process" and go rogue if you want to get on with your day.
I mean it helps that the code where the issues usually are is in the same languages I'm familiar with somewhat, but sometimes just logical reasoning helps a ton as well.
So I did the same thing today and it feels GOOD to fix shit.
#SoftwareDevelopment #Testing #QA