this post was submitted on 02 Jul 2026
240 points (99.6% liked)
Programming
27631 readers
194 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Let me preface this by saying that you should never, ever be rude to open source maintainers.
But good god, if you are writing software for other programmers, stop making breaking changes. By all means, break your software. Don't break mine.
If there's something I learned in the industry is how to test (and I don't just mean some unit tests) and how to write APIs with back compatibility in mind.
Not saying proprietary software is necessarily better, but working in a big organization that guarantees functionality to its customers, does teach you to coordinate releases better than most solo projects probably will.