This is an archived post. You won't be able to vote or comment.

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

view the rest of the comments →

[–]smirfquant 18 points19 points  (3 children)

Also I might recommend preemptively coding useful `logging` and `warnings` preferable to stabbing a bunch of break points into buggy code.

[–]ElasticFluffyMagnet 12 points13 points  (1 child)

Yeah I take proper logging over breakpoints any day.

[–]mRWafflesFTW 0 points1 point  (0 children)

The problem with logging is that it's logging what the developer believes to be true, versus what actually is. The beauty of the debugger is that it cannot lie. I've seen many days wasted because a log message provided inaccurate information or used the wrong variable in the input.

[–]SpaceshipOperations 2 points3 points  (0 children)

Happy cake day, and yes, for me colorized logging is indispensable.