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.
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:
lemmy.world/c/adhd will happily promote other ND communities as long as said communities demonstrate that they share our values.
- 1 user online
- 51 users / day
- 118 users / week
- 304 users / month
- 656 users / 6 months
- 1 subscriber
- 607 Posts
- 9.24K Comments
- Modlog
I’m this way 100%. Feels like I’ll be able to do it better and be less distracted by questions if I get to know something from the ground up, and just doing it a certain way because everyone agrees it works that way is never satisfying/I never feel like I can trust that completely.
Yea, can strongly relate. Hindered me a lot during my school years. I just couldn’t do anything without knowing the reasoning behind it. In the way I function, any amount of work is dictated by a need, and if the need -or the rationale, is never presented to me, then I fail to tackle the problem. I love solving problems, but they need to be real, applied.
I’m the same way. I can’t just know how to do something, I need to know why I’m doing something.
I can’t just blindly follow instructions or I’ll never learn. I need to understand everything so that I can find more efficient ways to do the thing I need to do. This is a common frustration I have in the workplace.
It’s put me at odds with some managers, until I got high enough where it became a target and I could determine the path to get there.
I hated managers who wouldn’t tell me the why, because I’d inevitably hit something that doesn’t line up with my training and I’d have to apply the why’s to determine what to do.
That’s why I never used Unity for anything but rather just started with raylib. And then went to pure Vulkan.
Ooh! Get an Arduino/electronics starter kit! You’ll learn how computers worked in the 80s. Then you’ll be able to move on up to say, Python in no time 👍
I should do that. My problem is what to make. There’s a billion things and it’s all been done already, so I just don’t know what I’d want to even do
Pick something in your daily life that you want to make more convenient. Start searching for tutorials, necessary hardware, and related coding.
Even something simple like, “I wish I didn’t have to turn on my fan because it’s in the corner.” Boom: look into building a motion sensor that runs a fan, and maybe it connects via a USB port for power.
Convince yourself it doesn’t need to perfect. It just needs to create a convenience that happens to teach you something.
I would find and follow a tutorial. They give you the “what” to do and you can go down rabbit holes of research connecting the why/how. Then when your done, you are starting with some knowledge/understanding which makes seeing possible applications easier.
I am this way completely. If I don’t fully understand all the details of something, I have no chance of remembering it. Elementary math classes were difficult in college because they infrequently included formal proofs, but as I progressed into more advanced courses I found I really loved math. The formal proofs made the difference. I need to be convinced that something is true; I can’t simply take it at face value.
I failed algebra 3 times haha, never got a solid base on math sadly. I understand it if it’s applied to something, but I literally couldn’t even do long division right now if I tried
Algebra came easy to me. I came to realize even in elementary school we were doing algebra even if they didn’t use that name. Simple arithmetic like 2 + 5 = ? Is algebra if you think of the ? As X.
Then it’s 2 + ? = 7.
After that, at least to me, it’s order of operations and just moving things around.
Same. Geometry I had major issues with because of proofs, but could use algebra to solve almost anything they threw at me.
It is ok to “cheat” even if you know the “real” way it should be done. It took me ages to come to grips with this but you can get over it too. There are still hobbies I won’t pursue because of this mentality though like drawing.
Yeah it’s hard. Because if I can cheat to do it easy, So can everyone, and then why do it at all.
Oh yeah, I totally get that.
When I’m doing something for fun, I’m far more interested in the process than the end result, so I’ll do everything from first principles. And probably never finish before I move on to something else. But that’s fine.
If it’s something I need to get done, on the other hand, then by the time I’ve started we’re probably already into crisis mode, and so getting it complete as quickly as possible becomes the goal. Then I’m all for finding whatever shortcuts I can.
Fortunately I’ve explored a enough topics (particularly in programming) for fun by now that I have enough background knowledge to be good at it for a career. Experience does build up, and even if you’re jumping around all over the place, eventually you’ll start to see the bigger picture.
Oh I feel like im master of " DO BIG COMPLICATED THING" and if by some miracle I finish it, I no longer care at all about. Queue 3 project cars…
I’ve wanted to learn the guitar my entire life, but I can’t just start slow and easy with some chords, I keep going all in trying to learn classical guitar simultaneously with music theory because chords seem too simple and I hate myself… I didn’t mention the research phase where I learned all about the origin of the instrument and its importance through history.
Just start playing and keep playing. I’ve been playing 25 years and have only picked up basic music theory but still have a blast.
May I introduce you to prog?
Covet and CHON are a good place to start for instrumental math rock; I reccomennd effloresce and Homey, respectively.
From there I’d suggest Plini, Intervals, and Arch Echo to add some grit.
But if you really really want to hate yourself and break your guitar over you knee? Id like to introduce you to Tosin Abasi;
https://youtu.be/bt-RoSzsEKA
https://youtu.be/0jpOBd949O4
One thing I can help you with. If you learn bass first, you really learn the structure of songs, and it helps make guitar even easier. Don’t worry about theory honestly. My friend is super into theory and im not really, and we both make complex music. Theory is just words for what you’re already hearing.
I have this problem. You are being a perfectionist. Some advice I have gotten that helps is trying to make something intentionally bad. It think it was from Simone Giertz’s TED talk. She said that trying to make Shitty Robots was easier because she couldn’t mess up, they were already bad.
https://youtu.be/GEIvFfeSjuE behind the scenes, idk where the full vid is.
Another thing to remember with programming is that bad, but working code will always be better than no code.
Yeah. I have found the prototype perspective can help. The idea being that this first attempt is part of the learning exercise and you will redo it “properly” the second time. It helps prevent building a emotional mountain of requirements to get started that only exist in my head. It’s kind of an mindset of knowing you will mess up the first one and that is OK because it is expected and a required part of the process.
In programming you do not need to know the inner workings in order to use something, in fact most people use abstraction to make a project more manageable and modular.
Also don’t learn anything before you start a project because it’s too boring. I always start a project and learn things I need to learn along the way
Starting a project which you actually find interesting and will really use, will also help with following through. There will be boring parts to it but the excitement of having something usable will overshadow any negative feelings.
I’ve struggled with this mentally, especially when I first was learning how to code. Eventually I realized while it’s great to know the ins and outs, you can allow yourself to only worry about what you need to know to get your code running (and that’s okay).
Write a script to go a thing, then learn about how to automate that with a cronjob, then learn about coding in the cloud. If you start too big you might get overwhelmed
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.
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.
Can you trick yourself into doing it the other way?
‘GUI building blocks let me see the shape of the finished code. Once I know the shape, I can work backwards to finer detail.’
‘Making music with the simplified tools lets me get the tune out so I don’t forget it, then I can replace parts with the proper instruments and tools.’
I’m still trying to get my head around coding, but I use the music trick to learn songs. I play them one note at a time on either bass or guitar to figure out the tune, then play them properly with chords or figure out the bass line once I know where the song’s going :)