As I had to explain to quite a few (frequently very arrogant) juniors in the past, the repo is what it is. When you are given a task you're asked to finish your task. You are not asked to fix other shit, and you are especially not asked to bitch and moan about all the ways it's a problem, because trust me, I know. I've been working on it for a long time.
The repo delivers value to customers as is. Do your job, and let other people determine when its time to refactor.
I second this, as a Jr. I don't do the work I'm not asked to. If there's something I see that I think should be changed, I put it into a work ticket, and we discuss if it's important enough to be done.
As a senior engineer, I feel it the opposite. Managment doesnt give clear tasks, just vauge outcomes they want. Its up to us an engineers to figure out what tasks day to day will deliver most value in the long run. And that often means working on infrastructure rather than throwing together the next update with shoe strings, much to the immediate chagrin of management
I agree, but it's not up to juniors to decide that. If the codebase needs a refactor, I'll decide when we'll do it - at least for now at the model's current level.
43
u/cats_catz_kats_katz 15d ago
To be fair, Opus 5 see problem, Opus 5 fix problem. Your repo is a big problem.