ADHD

11132 readers

14 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

121

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

submitted 1 week 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

[–] atzanteol@sh.itjust.works 5 points 1 week ago (1 children)

I can relate. I have a natural aversion to "high level" languages that obfuscate a lot of the details from me.

I actually do know a lot about the low-level details of programming, how code interacts with hardware, etc. BUT - I didn't start with that. I first learned BASIC (indeed - in the '80s). Then Pascal, then C. THEN I learned about assembly, computer architecture, etc.

Does knowing those low-level details make me a better programmer? Probably - but they're certainly not necessary to get started or to even be effective. And if I started with them I may not have gone into programming.

I've learned to how to convince myself that "I will simply accept this as it is for now (and that's okay) but I will let myself dive deep on it later". A bit of a bargain to give me permission to "cheat" for the time-being. It's helped when learning new frameworks which can be very complicated. And starting top-down can give you a better appreciation for the details underneath.

[–] applemao@lemmy.world 2 points 1 week ago

See this is why I always wish to had been born in the computing age and not the iPad age, would have actailly had a reason to learn the real building blocks ! Thats a good cheat though.