42
Finishing programming projects
(discuss.online)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Jul 2023
42 points (97.7% liked)
ADHD
9695 readers
158 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:
lemmy.world/c/adhd will happily promote other ND communities as long as said communities demonstrate that they share our values.
founded 1 year ago
MODERATORS
i read this somewhere, and i can't recall where now, but it anecdotally feels very true:
as soon as you tell someone about something you're working on but haven't finished yet, you get a premature dopamine hit. for some reason, that messes with the reward centre in your brain and makes it less likely to actually finish the fucking thing, like you've already sucked the juice out leaving an empty husk. so, my secret to finishing programming side projects has been to tell no one of them until they're ready. this is heavily paraphrased, i know nothing.
Yeahh I heard about it. But I have to tell people about it when I'm asking for help. I'm trying to do as much on my own as possible but there are moments where it's more than I can deal with.
Don’t tell them the whole project. Breaking a problem down to smaller components will help you conceptualize possible solutions, narrow down the problem space, and avoid the dopamine hit effect by discussing a single discrete problem, e.g. “how do I pull [x] from the database.”
I only described it here for context, usually I focus on the functionality itself, unless the bigger picture is needed even though it's a little difficult for me to tell which details are important and what can be omitted. Sometimes despite my best efforts there's some confusion and making it right is consuming a lot of energy.