this post was submitted on 19 Jul 2023
25 points (96.3% liked)
Learn Programming
1625 readers
1 users here now
Posting Etiquette
-
Ask the main part of your question in the title. This should be concise but informative.
-
Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.
-
Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.
-
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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I had to learn to be my own PM and do the whole task grooming bit. Checking things off gamified the process.
True, although it's very difficult to plan things when you don't know what's to be done;_;
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.
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