What you say is fair but let me give you some relative data so you can evaluate better.
The story would have taken a few days, let's say 3. These refactors costed another 1 day, plus one day and a half that I spent trying to actually remember what that code does, because of the way it is written.
Now in 2 days I can, with a code that smell way less, do the feature.
Having said that, in my limited experience, the NFRs I would ask to get my refactors done, would hardly be put in the calendar anytime soon, understandably, don't get me wrong.
That's the point of my post: I forced my company's hand to make something (I hope) good for it.
Ok, so it's definitely a communication problem. Have you tried to talk to them, outside of the moment you're developing a feature, about the technical debt?
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.
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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ciao rhymes, thanks!
What you say is fair but let me give you some relative data so you can evaluate better.
The story would have taken a few days, let's say 3. These refactors costed another 1 day, plus one day and a half that I spent trying to actually remember what that code does, because of the way it is written.
Now in 2 days I can, with a code that smell way less, do the feature.
Having said that, in my limited experience, the NFRs I would ask to get my refactors done, would hardly be put in the calendar anytime soon, understandably, don't get me wrong.
That's the point of my post: I forced my company's hand to make something (I hope) good for it.
Ok, so it's definitely a communication problem. Have you tried to talk to them, outside of the moment you're developing a feature, about the technical debt?
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.
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.