this post was submitted on 07 Dec 2023
81 points (90.1% liked)

Programming

17668 readers
200 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 [email protected]



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

@[email protected] Let me know if you need rehab.

But seriously... yeah, I get it. Especially this part about the workplace:

Nevertheless, [addicted programmers] can also pose significant risks, especially because they frequently deviate from the planned course. They follow their own agenda, introducing challenges where none were necessary, or dedicating hours to minor, tangential aspects of a project. In the process, they diverge from the project plan, programming what they believe is necessary rather than what the project itself requires.

I have been that person before, and now I'm in a position where I have to keep those folks on a tight leash and remind them "our goal is to deliver a product right now, and we can enhance it in future sprints. Let's just focus on what our primary goal was right now." It's easy to fall down rabbit holes, and that's where having proper planning and a ticketing system to backlog and prioritize future enhancements is so critical.