4 ms·
"refactor" is a trigger word for my tech lead now. It's exhausting when every attempt to improve the codebase is a battle. When I'm tasked with fleshing out the
by infogulch 6y ago
"refactor" is a trigger word for my tech lead now. It's exhausting when every attempt to improve the codebase is a battle. When I'm tasked with fleshing out the third bugfix story for a feature that I refactored in 30 minutes 2 months ago, but the PR for it which demonstratively would have solved all of them is still lying on the floor... a little part of me dies inside.
- fshbbdssbbgdd 6y agoI try to avoid calling anything a refactor. I just describe it as part of the fix. Similarly I never try to convince management that I need time to improve code quality... I just do it to code that I’m touching. I think people who don’t know the details have the (often correct) heuristic that work that doesn’t deliver incremental results is just an excuse to waste time / sandbag, so I just don’t bother trying to convince about the ROI.
- infogulch 6y agoI tried that until they reviewed it (they're a required reviewer for all PRs...) and forced me to split the refactor into a separate PR and let it sit there for 2 months before asking me to delete it. This occurred multiple times.