DEV Community

loading...

Discussion on: The myth of "never going back to fix it later"

Collapse
daviddalbusco profile image
David Dal Busco

Engineers need to fight for a culture that allows for regular refactoring, cooldown work, and general maintenance in times when more information is known about the model we are developing for.

"Just do it, all the time".

I have the feeling that I refactor code at least on a weekly basis, if not on a daily basis. Not necessarily, and probably even most of the time, within dedicated refactoring story but rather through my tasks or these which have been assigned to me.

Corporate might be scared sometimes (often) with the word "refactoring" ("I my gosh how much it gonna cost, again.").

Doing small steps within daily business, not having dedicated refactoring stories but rather being part of the development process and approach, is a win for everybody.