DEV Community

Discussion on: You're going out of scope, again.

albinotonnina profile image
Albino Tonnina Author

Of course, and actually nobody is against it.

I'm really not blaming anyone. It's maybe an issue of pace, or momentum if you will.

Even myself, let's say in a month or so, with some time to make those nice refactors, I may probably be interested in a new project I've been assigned to. Totally absorbed by other issues there.

The motivation could get lost or I don't know, the feeling that I may be working in some other place and that would became my legacy, some smelly code.

Thread Thread
guitarkat profile image
Kat • Edited on

Some smelly code isn't the worst legacy to leave behind. Generally people won't fix it so it becomes technical debt which is why people probably left you alone on it.

You're right though, I think. You're fighting your past self, but mostly I just go "what the hell was I thinking" and if I have time, work in refactor time through actual banked off refactor time in support of a feature or something so it works better (improvement) or actual just devoted refactor as a means of maintenance so it has proper testing, if possible, but it depends on your fires, your resources and whatever else is going on.