ADHD

11257 readers

178 users here now

A casual community for people with ADHD

Values:

Acceptance, Openness, Understanding, Equality, Reciprocity.

Rules:

No abusive, derogatory, or offensive post/comments.
No porn, gore, spam, or advertisements allowed.
Do not request for donations.
Do not link to other social media or paywalled content.
Do not gatekeep or diagnose.
Mark NSFW content accordingly.
No racism, homophobia, sexism, ableism, or ageism.
Respectful venting, including dealing with oppressive neurotypical culture, is okay.
Discussing other neurological problems like autism, anxiety, ptsd, and brain injury are allowed.
Discussions regarding medication are allowed as long as you are describing your own situation and not telling others what to do (only qualified medical practitioners can prescribe medication).

Encouraged:

Funny memes.
Welcoming and accepting attitudes.
Questions on confusing situations.
Seeking and sharing support.
Engagement in our values.

Relevant Lemmy communities:

Neurodivergent Life Hacks

lemmy.world/c/adhd will happily promote other ND communities as long as said communities demonstrate that they share our values.

founded 2 years ago

MODERATORS

MrPoopyButthole@lemmy.world

MrPoopyButthole@lemmy.dbzer0.com

123

How common is it to need to know the absolute inner workings of something in order to do it? (lemmy.world)

submitted 2 weeks ago by applemao@lemmy.world to c/adhd@lemmy.world

55 comments fedilink hide all child comments

Im wondering if this is a common adhd thing.

For example, I have always wanted to program, but I can't let myself start with some easy gui building block code. I need to understand how the code is interacting with the computer itself and know how they did it in the 80s. Then of course it's too hard for me and I give up.

Or if im making music, I need to do everything from scratch the hard way, making it as hard as possible (and killing any creative effort i had in the beginning).

It's the same with anything. I can't progress if I dont know the absolute reason why something is being done. And if I do it the easy way, I didn't do it right and took shortcuts so it was worthless.

you are viewing a single comment's thread
view the rest of the comments

[–] Acklavidian@lemmy.world 2 points 2 weeks ago

I can certainly relate. I remember disassembling mechanical things as a young kid and it always bugged me that there was this digital level of design that I couldn't physically investigate intuitively. Then once I started programming I remembered initially being disappointed by the concept of scripting/dynamic language. It felt like if I tried to imagine the twinkle of the 1s and 0s as they moved around the machine the patterns would more divorced from the physical hardware. Probably not an accurate or valid abstraction but it is the model that I mentally interact with at a high concept level. I've grown more partial to dynamic languages since then but only as I've come to terms with the underlying mechanisms. ADHD needs solid walls to bounce off of and having a interpreter that exists in this virtual environment doesn't naturally capture my trust. So in my hubris I doubt the veracity of the tools and learn that it requires a context change to dig in to the lower level of the issue which is demoralizing as an ADHD person. And now because I want to mitigate future context change I spend a lot of time forecasting potential context changes and quickly get overwhelmed by my own efforts.