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

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

[–] TweedyImpertinence@kbin.social 1 points 1 year ago

Always, but I’m a former Googler, so performance was always a huge concern with each and every frontend change we made.

Rendering something to a page without errors should be the starting goal, where you then shift focus to readability, accessibility, maintainability, interoperability - all that other stuff that actually matters more but is opaque to users - but in most cases, it’s the end goal, and all that other stuff isn’t considered at all.

IMO, the web would be a lot better if frontend devs spent more time learning how to use their tools instead of logging everything to the console.