Re:Why do we fall into the rewrite trap?
by Ididntdothis on Tuesday January 21, 2020 @11:08AM
(#22108153)
“Better to just incorporate refactoring into the estimate for any given coding task and do it without explicit permission.”
It should be as implicit as attending planning meetings. For some reasons PMs usually have no problem forcing people to sit through meetings but they have a problem with spending the same amount of time refactoring .
Re:Why do we fall into the rewrite trap?
by williamdclt on Tuesday January 21, 2020 @05:57PM
(#22112665)
In my teams we take tickets for meetings, which makes product owners very aware of their impact on delivery.
I like including refactoring in tickets, but if the refactor is consequent it's not going to work. It's not so often thankfully, I usually manage to convince the PO of the value of it, then try to not budge once it's decided
Re:Why do we fall into the rewrite trap?
by Archit3ch on Tuesday January 21, 2020 @08:52PM
(#22113807)
Evidently the answer is refactoring during meetings. /s
Re:Why do we fall into the rewrite trap?
by ShamelessC on Thursday January 23, 2020 @06:40AM
(#22126725)
Sarcasm not needed. I've probably done this during a meeting. I definitely code if it's an all hands on deck meeting that gets hijacked by technical discussions that aren't relevant to my work.
Better to just incorporate refactoring into the estimate for any given coding task and do it without explicit permission. Unless of course you're in a culture that is willing to straight up miss a deadline in order to get refactoring finished.