this post was submitted on 20 Mar 2026
18 points (87.5% liked)

Programming

26148 readers
301 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 2 years ago
MODERATORS
 

Not sure if it’s just me, but I’ve been running into this quite a bit.

My client conversations are spread across different messaging platforms, and sometimes important or more detailed discussions just get buried or overlooked.

It’s not even about the number of messages, it’s the fragmentation that makes it hard to keep track of everything in one flow.

Anyone else dealing with this? How are you keeping track of conversations without things slipping through?

you are viewing a single comment's thread
view the rest of the comments
[–] MeFisto94@programming.dev 4 points 15 hours ago

Well, sounds like the issue is that important specification details aren't part of the specification but clarified on the fly in some random chats.

At least it should be added to the issue/ticket description and not just as an appendix but a coherent text. Ideally, there should be a lot being clarified before even starting