DEV Community

Discussion on: It's not your job!

Collapse
 
sandordargo profile image
Sandor Dargo

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.