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

Programming

14184 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 2 years ago
MODERATORS
alyaza@beehaw.org
Hexorg@beehaw.org
remington@beehaw.org
12
How frequently do you use profilers/debuggers at work? (anarch.is)
submitted 2 years ago by pinkpatrol@anarch.is to c/programming@beehaw.org
34 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 2 points 2 years ago (2 children)

How do people do stuff without debuggers? :D

Another way to develop would be through iterating within a Unit Test that you don't plan to keep around.

Uh, I set a breakpoint and run the app?

To add a bit more context, it's more difficult to configure a debugger when the application is running within something like Docker. How difficult? That depends on the language and tools you're using.

[–] Nicktar@beehaw.org 6 points 2 years ago* (last edited 2 years ago) (1 children)

I've seen the fun of "prints everywhere" in production when a colleague forgot to remove a "Why the fuck do you end up here?" followed by a bunch of variables before committing a hot-fix... Customers weren't to amused...

Edit: That was a PHP driven web shop and the message ended up on to of the checkout page

[–] leodude@mastodon.social 1 points 2 years ago

@Nicktar I usually prefer the prints everywhere approach, but of course printing to STDERR not STDOUT - so it ends up in a log, and not in the program output 😅 won't make that mistake again!