An excerpt from the encyclopedia of "Developer Confessions":
At times, when I have no clue what some code does, I comment it out to see what breaks. Sometimes I just want to see the code burn.

  • 1
    It is weirdly satisfying ik, but why not just use breakpoints and watch the piece of code in action?
  • 0
    I do that with bugs. I comment out part of the code, and if the bug dissepears it means the bug is in the commented code
  • 0
    @100110111 sometimes that is revealing but when the call stack is deep than you are just looking at the same puzzling code with the data.
    Repeating the (edge case) action in the application without the code might be more revealing.
Add Comment