The problem is that most refactoring activities will be out of scope. If you don't take the "ownership" for yourself (e.g. work few hours later for a few days in order to accomplish the refactoring, without delaying the team's progress), chances are that you'll never have a "proper scope" for this.
I'm not defending that we should accept overwork as normal thing (it's not), but sometimes we need the push "the extra mile" in order to have a job well done feeling.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
I don't see any point doing refactorings in extra hours. With that, we might give an impression that (code) quality comes for free. It does not - in the short run, in the long run, it is cheaper than writing a big mess. But tackling technical debt is rather expensive. We can see that in most of the long-running projects where people, in the beginning, were penny-wise but pound-foolish.
I personally never stayed late so that I can refactor the code. I just make it part of my development process. Just like adding tests for example - for some even that is not in the scope...
We have to find the golden mean. Which is definitely not the first version of the code that we drafted and eventually started to work, but also not something that we overengineer during weeks.
However, in my opinion, nobody should be afraid of saying "I'm not ready yet" until the code is not something that he/she would also be happy to show at an interview part of his/her portfolio.
And if the company doesn't welcome quality work. Well. Just look for another one.
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.
The problem is that most refactoring activities will be out of scope. If you don't take the "ownership" for yourself (e.g. work few hours later for a few days in order to accomplish the refactoring, without delaying the team's progress), chances are that you'll never have a "proper scope" for this.
I'm not defending that we should accept overwork as normal thing (it's not), but sometimes we need the push "the extra mile" in order to have a job well done feeling.
I've smashed a wasps nest that's all I'm saying. I absolutely agree you should be fearless. But not wreckless.
I don't see any point doing refactorings in extra hours. With that, we might give an impression that (code) quality comes for free. It does not - in the short run, in the long run, it is cheaper than writing a big mess. But tackling technical debt is rather expensive. We can see that in most of the long-running projects where people, in the beginning, were penny-wise but pound-foolish.
I personally never stayed late so that I can refactor the code. I just make it part of my development process. Just like adding tests for example - for some even that is not in the scope...
We have to find the golden mean. Which is definitely not the first version of the code that we drafted and eventually started to work, but also not something that we overengineer during weeks.
However, in my opinion, nobody should be afraid of saying "I'm not ready yet" until the code is not something that he/she would also be happy to show at an interview part of his/her portfolio.
And if the company doesn't welcome quality work. Well. Just look for another one.