ADHD

11257 readers

135 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

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

So, for this, the easiest way I've found is to look at it in the following sort of way:

Using the example of coding, you can already USE software, think of that like knowing how to DRIVE a car. Start with learning how to REPAIR the car (GUI building block code).

Then learn how to MOD the car with a kit (high-level object-oriented, TYPED code with an IDE or editor that does stuff like auto complete, syntax highlighting, and has add-ins that assist in getting the typed code to completion).

Then learn how to create your own car mods from "scratch" (get to the point where you don't necessarily NEED all those editor widgets to help code)

Then learn how the car functions at a base level and how all the various chemicals, heat, and aerodynamics, pistons, filters, etc interact to make the car function (interacting with and modifying OS-level code/low-level languages with things like hardware access instead of applications that run on the OS)

THEN worry about the various chemicals themselves create the energy needed to generate power for the car (firmware on top of circuits and chips like the CPU/GPU/PSU, storage controller boards, audio chips, and motherboard/bios)

THEN worry about the actual molecular interactions occurring in the batteries or fuel at the atomic level (binary electrical functions of the parts themselves, where 1's and 0's are just current on or current off).

Just because the binary is there at every stage doesn't always mean that understanding how the bonds between the "atoms" operate is going to make you a better programmer UNTIL you understand what you're trying to get those atoms to do and why.