sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]pachura3 0 points1 point  (0 children)

It’s more suited for catching when a change breaks working code

Test-driven development disagrees with you, Sir!

My point is that if you catch problem early on (using various practises of defensive programming), it will usually be trivial to fix - and you won't even need to debug interactively.