From 14bff9328ab648e0f031e80eea9f854b9c0fadc4 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Thu, 14 Sep 2023 00:28:16 +0100 Subject: [PATCH] daily-email: add 2023-09-08 Do you proactively refactor your code? --- src/content/daily-email/2023-09-08.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 src/content/daily-email/2023-09-08.md diff --git a/src/content/daily-email/2023-09-08.md b/src/content/daily-email/2023-09-08.md new file mode 100644 index 00000000..bfe9566b --- /dev/null +++ b/src/content/daily-email/2023-09-08.md @@ -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.