this post was submitted on 01 Sep 2023
337 points (96.2% liked)
Programming
17524 readers
334 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't think you understood my point. That's exactly why I think unit tests aren't all that useful. Most code changes require updating the unit tests so unless you change the unit tests first all that's being done is saying, yep this works how I programmed it to work.
But if unit tests that other people wrote unexpectedly break, you know that you changed things that you maybe didn't mean to change.
Ideally. It's just that more often than not it means you need to update the unit tests. I can still use my fingers to count how many times a unit test has caught a mistake I made, and I've been at my job for 10 years.
I'm curious if others have a different experience.