this post was submitted on 01 Aug 2023
72 points (97.4% liked)
Programming
17515 readers
327 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 [email protected]
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
Since adopting TDD, my debugger use has really dropped off. I think it's partially due to TDD encouraging me to develop more pure functions and push side effects to injectable (and thus mockable) objects.
But every so often I encounter a state that I can't understand how the code gets into, and in those cases being able to step through everything that's going on is incredibly helpful.
I may not use my debugger every day, but when I want it, I'm sure glad it's there.
When I have a real head scratcher like that I use log with a b c d. It's rare though and mostly due to me not paying attention or due to some convoluted calling graph.
Ya I've also switched to functional wherever possible. I still use objects for di.
Same here! Testing up front has made it extremely rare that I have to go back with a debugger later.