I know profilers and debuggers are a boon for productivity, but anecdotally I’ve found they’re seldom used. How often do you use debuggers/profilers in your work? What’s preventing you? conversely, what enables you to use them?

  • JesterXIII@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I used to just use print statements and avoided debuggers because I didn’t understand it. But as I’ve gotten more experienced, it’s become my first choice in debugging now (go figure haha).

  • xian@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    As a C# programmer I use the debugger every single day, since it’s so natural and easy to use as to just run the application. I’ve grow spoiled actually, when I program in Go or Rust I really miss the “it just works” debugger.

  • camel-cdr@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I recently started doing xeyes debugging.

    We have so many debug logs that trying to find your log of a background takes a non zero amount of time.

    So just inserting system("xeyes"); is actually way easier, to get instant feedback, and you can just use system("xmessage msg"), if you need a message.

  • SwingingKoala@discuss.tchncs.de
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I’ve used a debuggers only a handful of times in the last decade or so. The projects I work on have complex stacks, are distributed, etc. The effort to get that to run in a debugger is simply not worth it, logging and testing will do 99.9% of the time. Profiling on the other hand, now that’s useful, especially on prod or under prod load.