ADHD

11115 readers

192 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

119

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

[–] eleitl@lemm.ee 2 points 1 week ago (1 children)

I never understood how programmers had no clue how the hardware worked. How can you write high performance code without understanding memory access optimization and opcode pipelines? Why even attempting rewriting old Fortran array code to C and then to C++ without understanding that Fortran array code fits cache lines just fine, while your newly shiny refactored code doesn't, so now you wonder why your code performance sucks?

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

This is the stuff I wish I knew. Oh to be old !