- Is it maybe not such a big part of HN's commenting group that is spending time debugging
- Or is coding a small fraction of their daily grind in the first place...
- ...or at least, are they not tracking debug time very closely as a proportion of time spent coding?
- And what is considered debugging these days? Running a debugger only? Something else? I often find myself debugging only to get thinking deeply and end up evolving the activity into something more like new feature development.
The audience would seem to be people who are analytical, full-time coders who are also taking and consulting measurements of their own work. This is either a really conscientious population or a population really focused on an annoying concern for the time being. Bugs everywhere, every day, with no relief maybe.
So, just some ideas. I hope you get the answer you are looking for.
If I was going to ask a super serious question here I think I would try painting a picture, so to speak, of what I'm doing and ask what I'm doing wrong. A little bit similar to this Q in some ways.
We have access to a lot of critical thinkers here who are interested in improving systems, human or otherwise, and hopefully helping others help themselves. So this "hey what's wrong with me" approach is one that seems to get a lot of sympathy and traction. Perhaps in contrast to "Hey what are your measurements saying."
Good luck to you in your learning journey.
Helps if you're asking people to share a story. Those are easy to respond to.
There's also a considerable amount of luck. Sometimes you just get lost in the sworl. Keep posting.