opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

daily-email: add 2023-09-08

Browse source 
Do you proactively refactor your code?
This commit is contained in:
Oliver Davies 2023-09-14 00:28:16 +01:00
parent 94ae659351
commit 14bff9328a
1 changed files with 24 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
src/content/daily-email/2023-09-08.md Normal file
View file

@ -0,0 +1,24 @@
---
title: >
Do you proactively refactor your code?
pubDate: 2023-09-08
permalink: >
archive/2023/09/08/do-you-proactively-refactor-your-code
tags:
- software-development
- refactoring
---
Do you go back and proactively refactor code you've previously written?
In my experience, once some code is working, it's usually not reviewed again and refactored, and any TODO comments are still there.
If code is refactored, it's usually triggered by adding a new feature or fixing a bug that will be difficult or impossible with the existing code - i.e., make the change easy, then make the easy change.
Very rarely have I seen code be refactored to make it easier to read or change in the future.
Do you proactively refactor code or wait until something forces it to happen?
Do you not refactor code at all once it's been written?
Reply to this email and let me know which and why.