this post was submitted on 22 Jun 2023
1 points (100.0% liked)

Programming

13373 readers
1 users here now

All things programming and coding related. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 1 year ago
MODERATORS
 

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?

all 9 comments
sorted by: hot top controversial new old
[–] cnk@kbin.dk 1 points 1 year ago

I have a tendency to just use console logging, and only use debuggers when things are starting to get hairy.

[–] JesterXIII@kbin.social 1 points 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).

[–] camelcdr@beehaw.org 1 points 1 year ago (1 children)

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.

[–] Zapp@beehaw.org 1 points 1 year ago

That makes me so happy.

[–] xian@beehaw.org 1 points 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.