this post was submitted on 09 Oct 2025
47 points (100.0% liked)
Programming
23053 readers
117 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
Destroy abstractions
The reality is, if you have an abstraction layer and one implementation of it, you dont need that abstraction layer
People will complain, "oh but think about the refactor if we have to change vendors/etc" but i have yet to ever switch vendors/api/etc and not had to completely rethink the abstraction layer
Just get rid of it, it will be easier, less code, more precise, and in the long run you'll cargo cult less
Just write the code for the things you have, and if things change, yup then things will change - to anticipate future changes and upfront the work for the unknown only to then have to make more changes once those real changes eventually arrive and dont match your old predictions is just more work and more confusion