Programming

13376 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

alyaza@beehaw.org

Hexorg@beehaw.org

remington@beehaw.org

How frequently do you use profilers/debuggers at work? (anarch.is)

submitted 1 year ago by pinkpatrol@anarch.is to c/programming@beehaw.org

38 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

[–] Nicktar@beehaw.org 7 points 1 year ago* (last edited 1 year ago) (2 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

[–] MagicShel@programming.dev 2 points 1 year ago

That must've prompted a bit of existential crisis in some shoppers. I can see going to purchase some useless consumer shit online and getting a message "Why the fuck do you end up here?" and just closing my browser and rethinking my life decisions.

[–] leodude@mastodon.social 1 points 1 year 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!