From 69c92f325b4d20592fba61077f11fdd0b4046e31 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Sat, 22 Feb 2025 22:33:36 +0000 Subject: [PATCH] Add daily email for 2025-02-09 Simpler code doesn't mean less code --- source/_daily_emails/2025-02-09.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 source/_daily_emails/2025-02-09.md diff --git a/source/_daily_emails/2025-02-09.md b/source/_daily_emails/2025-02-09.md new file mode 100644 index 00000000..5c524291 --- /dev/null +++ b/source/_daily_emails/2025-02-09.md @@ -0,0 +1,27 @@ +--- +title: Simpler code doesn't mean less code +date: 2025-02-09 +permalink: daily/2025/02/09/simpler +tags: + - software-development +cta: ~ +snippet: | + Simpler code doesn't necessarily mean less code. +--- + + +Just because I consider some code to be simpler, that doesn't necessarily mean there's less code. + +It's possible to write a whole function or class on one line, but that doesn't mean it's simple to read or understand. + +The opposite is also true. + +I can extract business logic from Controller classes into different service classes, commands or actions. + +I can use data transfer objects (DTOs), value objects and Collection classes to give names and meanings to things instead of always using generic strings, arrays or objects. + +I can follow design patterns and implement Repositories, Decorators, Factories and Builders to better organise code and make it easier to use and update. + +I can write tests that act as examples and executable documentation for people to see how to use the code I've written. + +This can all make code easier to read, understand and use - even though there is more of it.