*Me using visual studio debugger for the first time*

  • 4
    @devtea so the legend is true XD, thanks :D
  • 7
    Visualstudio legend?
  • 6
    @devTea legend says post a good rant and devtea will ++
  • 3
    @FrodoSwaggins ?
  • 3
    @MEGADROID Debuggers are nice, but still a crutch. Once you become one with the code, you can just look, and you will see the bug. See the system from the code's point of view.

    I once had a nice pair programming with a junior dev, but he was familiar with the project and I was not. Since I value domain knowledge over coding, I gave him the lead. At one point, he suggested a fix, and I immediately told him this wouldn't work. He asked back why - and I didn't have an answer, I just said the suggested code didn't feel right. After a solid hour of analysis, I was able to prove my point.
  • 3
    @MEGADROID gdb is the GNU debugger, usable even from commandline. You can catch signals (most importantly: SIGSEGV), set a read or write watch on variables, debug the call stack, use it as disassembler and tons of other stuff.
  • 5
    @Fast-Nop thanks for the info :)
  • 2
    Yup, that's how it feels
  • 1
    I literally said out loud: "i've never felt power like this before"
  • 3
    Pro Tip:

    You can drag the yellow arrow down if you want to skip down to a later point instead of stepping over methods till you get there.

    I have been using Visual Studio for 7 years and I learned that a month ago.
  • 1
    @aquacash5 same here lol.. Also. The call stack window is a life saver
  • 4
    @aquacash5 that feature has been introduced with vs 2017, so it isn't that old. You can drag the arrow to previous statements as well. A really nice tool together with the editable code on runtime
Add Comment