4 ms·
> But the PM doesn't understand why you're changing the code you made If that is the case, the PM does not understand red-green-refactor, always-refactoring, o
by berkes 5y ago
> But the PM doesn't understand why you're changing the code you made
If that is the case, the PM does not understand red-green-refactor, always-refactoring, or even just plain refactoring. I'd say the PM doesn't even understand the idea of technical debt, in that case.
The problem is certainly the PM's disconnect to how to keep a codebase (and their team) sane in the most common programming practices. And not the refactoring itself.
- blowski 5y agoI agree with that assessment on the surface. But it's a sign of a generally unhealthy team, not just a poor PM (although the poor PM might be the root cause).