• @[email protected]
        link
        fedilink
        151 year ago

        I work with 20 year old legacy spaghetti code, the debugger has become one of my most treasured tools.

        • @[email protected]
          link
          fedilink
          41 year ago

          I also work with 20 year old spaghetti code, but my software is primarily middleware and debuggers aren’t allowed on the full system where I’d actually be able to reproduce the issue. Insane amounts of logging statements have become my most treasured tool.

    • @HairHeel
      link
      English
      241 year ago

      console.log counts as “a debugger”, right?

      • @[email protected]
        link
        fedilink
        English
        21 year ago

        Yes, but only because it gives you a link to where that was run. Click the link to the right with filename:lineNumber, and it will open the sources tab to that line. Set a breakpoint and rerun to pause there, then step through the code’s execution.

        Of course, if you’re using minified or processed code, this will be more difficult, in that case figure out how to do it in VS Code.

      • @[email protected]
        link
        fedilink
        51 year ago

        Yep. Once you get the hang of it, you will cringe to think of all the wasted effort that came before. But getting the hang of it takes dedication.

        • @[email protected]
          link
          fedilink
          11 year ago

          Thankfully I use python mostly and pycharm makes it easy-ish to get the debugger hooked up to a project. But learning that process definitely took a few days

    • @[email protected]
      link
      fedilink
      31 year ago

      Does this include C programmers? I’ve definitely found GDB to be indispensable in the past (or maybe that’s what they would want you to think).

    • @[email protected]
      link
      fedilink
      21 year ago

      After decades of print debugging I finally got dap up and running in vim. It is very nice. Would recommend.