52
Mistakes engineers make in large established codebases
(www.seangoedecke.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Mar 2025
52 points (96.4% liked)
Programming
19368 readers
207 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
This guy would fit in well at my previous job where the founder discouraged writing unit tests because "there are too many scenarios to test."
Like, wtf...
It's been the hardest thing for me to instill good testing practices in devs. In a function with 23 paths devs usually burnout and only do 9 or 10. Most never consider that making the function smaller is an option.
1 scenario tested is better than 0 tested.
Stroke of genius 🤣🤣🤣