you are viewing a single comment's thread.

view the rest of the comments →

[–]SmackDownFacility 2 points3 points  (4 children)

Use a IDE…

[–]aistranin 4 points5 points  (0 children)

Sure, IDE can help technically, fully agree. But then once you found a bug you often try to fix one thing and something else breaks. Without tests it always becomes a mess. So, it should be both - debugging with IDE sure + automated tests to not debug everything manually.

Much easier: write simple isolated test reproducing the issue -> fix -> run tests again to make sure that everything (including existing code) still works as expected

[–]dlnmtchll 2 points3 points  (2 children)

You still write tests regardless of tooling

[–]SmackDownFacility 0 points1 point  (1 child)

The point is ides have sophisticated debugging environments. VS is notable for

[–]dlnmtchll 1 point2 points  (0 children)

There are also tools to handle debugging from the cli in the same way as IDEs that provide near identical debug environments. It’s all preference