3 ms·
This is interesting. As a developer with ADHD, maybe I should try paring down my IDE interface. (I do take amphetamine medication though so maybe it compensates
by xmcqdpt2 3y ago
This is interesting. As a developer with ADHD, maybe I should try paring down my IDE interface. (I do take amphetamine medication though so maybe it compensates enough?)
I find it interesting though that they describe "debugging" as a monotonous activity. Maybe my experience is different from others? I personally find debugging to be way more active than coding! It involves setting breakpoints, zooming about the codebase trying to understand the flow of an app and cutting down code until you get a minimized repro. I'm often doing this live with users or other devs looking over my shoulder while I play with code all over the place and run git bisections. It's often a time sensitive activity too, because a bug might be blocking a release or requiring a fast prod rollback. From an executive dysfunction POV, a bug report is often the perfect kind of task for me, inherently scoped, usually short, with a clear success condition.
I personally thrive on that kind of work and I usually really enjoy being on the support rota (not for too long though!) In fact if anything, I enjoy it too much and bug reports don't uncommonly take me away from the actual dev work I should be doing.
I think the issue is that they probably didn't do the debugging tests under the right conditions.
- nucleardog 3y agoIf you read the paper the “debugging” task is “here’s a bunch of python code, there’s problems in the whitespace, please read through and find the whitespace problems and correct them—this is explicitly not a bug in the logic and no code needs correcting”. They didn’t test the wrong thing, they tested exactly what they want—a high engagement task and a low engagement task.