this post was submitted on 19 Jul 2023
24 points (96.2% liked)

Learn Programming

1615 readers
2 users here now

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

  4. Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 2 years ago
MODERATORS
Ategon@programming.dev
JaumeI@programming.dev
bugsmith@programming.dev
24
ADHD, finishing projects and being independent (self.learn_programming)
submitted 1 year ago by Krzak to c/learn_programming@programming.dev
19 comments fedilink hide all child comments
 

How do I trick my brain into completing a project? I'm making an app that shows which voice actor plays a character in the movie and what other movies they act in. It's useful for me personally so the internal motivation is here but sometimes I feel like I'm making something that's been done numerous times over and I lost the momentum because I'm on vacation with my family now.

I ran into some problems with the project too and getting help takes a ton of time so it's disrupting the rythm too. I wish I didn't have to rely on other people so much but the documentations don't answer all of my questions. I really have to put at least 2-3 projects like this for a portfolio;_; halp

you are viewing a single comment's thread
view the rest of the comments
[–] Krzak 2 points 1 year ago (1 children)

True, although it's very difficult to plan things when you don't know what's to be done;_;

[–] ndotb@programming.dev 2 points 1 year ago (1 children)

It's a lot easier than I initially thought: just write down a high-level, abstract sentence fragment of what needs to be done. Get it off your chest and put it in ink (or pixels?). Then ask yourself: how can I split this into two parts? Rinse and repeat.

The initial limiter for me was anxiety and fear about it. Once I got into the habit, the limiter was avoiding hyperfocus and micromanaging myself in the project plan. I try not to break things down beyond 1-2 hour tasks.

[–] Krzak 2 points 1 year ago

I'm doing this and it really helps. For me the main problem here is that I don't know all the pieces and time estimates are weird too. I guess it comes with practice but it's a pain in the ass :P