Although I'm not medically diagnosed, I do deal with the issues that are associated with inattentive ADHD.
I definitely agree with the second part of your post, where disorders can be a super power when used right! It seems that I started programming exactly because of the hyper-focus induced by ADHD.
For me most effective coding workflow is to have a quick way to test the newly added code and see a visual response to validate that it works as expected. Seeing instant results from newly added code can keep me focused on tough problems for a long time.
Software engineer obsessed with accessibility in tech, pretty code, fiber crafts, and her dogs' happiness. Looking for a team that's excited about building with accessibility and inclusion in mind.
Yes! Instant results definitely help! I think that's why front-end work got me so easily hooked at first since it was so visual and you could actually see what you did. But I hadn't considered that tests do the same thing! Thanks for that insight!
On that note, if you're working on less visual code, use test-driven development! And, by TDD, I really mean it: write actual, granular unit tests first, and then code. Seeing the lights turning green as you work gives that same instant, ongoing feedback as web development.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Although I'm not medically diagnosed, I do deal with the issues that are associated with inattentive ADHD.
I definitely agree with the second part of your post, where disorders can be a super power when used right! It seems that I started programming exactly because of the hyper-focus induced by ADHD.
For me most effective coding workflow is to have a quick way to test the newly added code and see a visual response to validate that it works as expected. Seeing instant results from newly added code can keep me focused on tough problems for a long time.
Yes! Instant results definitely help! I think that's why front-end work got me so easily hooked at first since it was so visual and you could actually see what you did. But I hadn't considered that tests do the same thing! Thanks for that insight!
On that note, if you're working on less visual code, use test-driven development! And, by TDD, I really mean it: write actual, granular unit tests first, and then code. Seeing the lights turning green as you work gives that same instant, ongoing feedback as web development.