3 ms·
My phrasing may have been better in some cases. "Works but is going to cause a problem when XYZ happens" may be more accurate. I was actually told by a PM onc
by mgkimsal 2y ago
My phrasing may have been better in some cases. "Works but is going to cause a problem when XYZ happens" may be more accurate. I was actually told by a PM once "how about you just say 'I told you so' after something breaks instead of always complaining about wanting to fix stuff?" which was truly bizarre.
My foodservice days had "if you got time to lean, you got time to clean" drilled in to me, but it's not always the same in software. What constitutes "clean" may be the core issue.
- sitkack 2y ago1) You need to foster a culture where those improvements are allowed in 2) Codify norms of how a shared goal is worked on 2a) refactor tests as part of separate PR 2b) realign code with refactoring in mind (this is the begin transaction portion) 3) commit work 4) merge everything into main It might take 3x longer, but it is more controlled. The larger the team, or the more consumers, the more important it is to get the interfaces right. And if you can refactor the interface ahead of the code itself, the refactor isn't even noticed.
- deleted 2y ago[deleted]