The really interesting part is IMO this one:
this post was submitted on 21 Sep 2024
203 points (100.0% liked)
Programming
17670 readers
277 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My biggest gripe is the lack of respect/understanding for the importance of data models and clear domain boundaries.
Most things that end up as "technical debt" can be traced to this. Sometimes, it's unavoidable, because what the data models changes, or the requirements of the domain, etc.
And, it's very innocent looking differences sometimes. Like "We know that the external system state will change from A to B, so we can update that value on our side to B". Suddenly you have an implicit dependency that you don't express as such.
Or, things like having enum that represents some kind of concept that isn't mutually exclusive. Consider enum values of A and B. Turns out this really represented AZ, and BP (for some inherent dependency to concepts Z and P). Someone later on extends this to include ZQ. And now, suddenly the concept of Z, is present in both AZ and ZQ, and some consumer that switches on concept Z, needs to handle the edge case of AZ... And we call this "technical debt".