this post was submitted on 22 Sep 2023
34 points (97.2% liked)

Programming

17354 readers
339 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

Does this hit close to home for you too?

I often find myself skirting around the actual meat of the issue, solving minor, simpler issues around it. Finally I must consciously decide to move in, and as a producer I knew would say - slap it in the face and drag it over the finish line.

you are viewing a single comment's thread
view the rest of the comments
[–] fiah@discuss.tchncs.de 4 points 1 year ago

well yes, but I don't think it's necessarily bad to go about it like you described, as long as you know that you're not actually using the smaller issues to procrastinate on the big issues. Tackling the smaller issues first can help you to understand the bigger issues better, both consciously and subconsciously, so as long as it doesn't actually matter in which order they're done, I think it can be more effective to do the smaller ones first. That all goes out of the window of course if you're using the small issues to avoid having to think about the bigger ones