Title: P2: Keeping software alive. [2025-08-18 Mon]

inheritance 🤔? Should we prefer functional paradigms
and bottom-up design?
This is the amazing post that should be reposted everywhere.
█ #dailyreport #code #programming #goodcode #codequality #codereview #readability #amazingcode #greatnews

Title: P1: Keeping software alive. [2025-08-18 Mon]

- Favor composition over inheritance, build functionality
by combining smaller parts rather than deep hierarchies.
- Use interfaces and dependency injection for easy
testing, replacement, and reuse.
- Follow best practices (SOLID, DRY, KISS) to ensure
clarity and reduce redundancy.
What you think about doing more composition over #dailyreport #code #programming #goodcode #codequality #codereview #readability #amazingcode #greatnews

Title: P0: Keeping software alive. [2025-08-18 Mon]

In the AI era, code ages quickly. :( To keep software
flexible for future 🏄 improvement, I think, we should:
Divide & Encapsulate
- Modularize code into independent, single-responsibility
modules.
- Define clear abstractions and interfaces to minimize
interdependence.

Design for Flexibility #dailyreport #code #programming #goodcode #codequality #codereview #readability #amazingcode #greatnews

Just discussed it with a friend and shared that I am quite rigorous on doing translations in a certain way.
One example is the last change, read the commit message:

Don't do any simple string translations like "in" which totally miss all context, they will go wrong in some language. Use "in $location" now, so one can see the context what the "in" is meant to be for.

#i18n #django #gettext #goodcode

I've taught a lot of people to code and I've found myself giving the same advice again and again. Here are a few things that come up a lot.

https://buff.ly/40710Yq

If you are early in your career, check it out. And share it with someone who would benefit.

If you have been around the block, what stands out for you? And what other advice would you give?

#CodeNewbie #ProgrammingTips #LearnToCode #GoodCode #DevAdvice"

# I could in theory do this with one big structured loop:
# ansible.builtin.copy
# src: '{{ item.src }}'
# dest: '{{ item.dest }}'
# loop:
# - src: source1
# dest: dest1
# - src: source2
# dest: dest2
# et cetera et cetera et cetera </king-of-siam>
# but this is more *readable*, and I want 2am me
# or any other poor soul who has to try to decipher this
# to not hate me and want to do unspeakable things, so:

(insert multiple copy stanzas by target directory here)

#goodcode