this post was submitted on 30 May 2025
26 points (96.4% liked)
Programming
22186 readers
191 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 !webdev@programming.dev
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
No. That is to say, it might be common, it might be expected, but it is often not good. Every time I join a new team and am exposed to a new code base, I'm astonished by the amount of absolute shit code that results from reusing shit in ways that it was never build with the idea of supporting.
Why? Because someone was focused on completing a single story as fast as possible and they created a dependency they shouldn't have. And this grows and festers until you have an unmaintainable nightmare.
In order to build solid reusable code you must build it with that knowledge and intent. I'll cut my rant off there, but I recently joined a new team and the wounds are all very fresh.
Oh yeah totally, I just meant more as a best case scenario where you have very well documented very specific functions with a very limited scope that are reused throughout.