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

Programming

13368 readers
2 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
alyaza@beehaw.org
Hexorg@beehaw.org
remington@beehaw.org
19
How frequently do you use profilers/debuggers at work? (anarch.is)
submitted 1 year ago by pinkpatrol@anarch.is to c/programming@beehaw.org
39 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] pinkpatrol@anarch.is 3 points 1 year ago (1 children)

That's an interesting point about depending too heavily on a debugger. I haven't run into anyone too dependent on it, but I could see that happening.

To me, debuggers offer a tighter dev loop when there's something you're stuck on. They also let you 'grok' a call stack in an unfamiliar codebase. "Did this function get called?" "What's in this variable?" etc.

[โ€“] TheTrueLinuxDev@beehaw.org 1 points 1 year ago* (last edited 1 year ago)

That I agree, I always see it as a critical necessity to always document everything when more than 1 developer work on the project. It like making a trade:

Spend time and effort debugging

Or

Spend time documenting and maintain it with the help of Chatgpt

With ChatGPT, it seems to reduce cost for documenting while same can't be said for debugging.