DEV Community


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

bpedroza profile image

Totally agree with this!

We just started a new practice on my team at work: 1 Week each month is 'Maintenance week'. This gives us time to go back and revisit the old code, refactor, and remove stuff that's no longer used. Obviously if a major bug comes in that week - it gets priority, but this has been a really great way to find time to 'fix it later'.