If you interrupt an explanation every 30s, you'll probably end up getting a worse explanation and understanding of the topic IMO. The constant interruptions will make it much harder for the other person to give a structured explanation and will make it way more likely that they'll forget some things which they originally wanted to say.
this post was submitted on 29 Sep 2026
7 points (68.4% liked)
Programming
28681 readers
157 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 3 years ago
MODERATORS
I think the title and this 30s framing sucks, but the other/later points they make are broadly good guidelines. A mindset of trying to understand context and environment surrounding the question or change at hand. It's certainly necessary to maintain and improve long running projects.
I got fired for asking questions about the projects specifications and questioning the lack of infos given...
Why?
Why not?
At work I have a note book filled with acronyms and things I don't know followed by question marks. I even occasionally go and look up what they mean
I have a colleague where I get more confused when they explain things to me. I have others I can understand just fine, because their explanations make logical and structural sense.
Reasonable questions about surrounding context and environment and common understanding aside, having to do questions to "fix" bad communication and explanations sucks.
I love when I can talk with my colegues and ask questions.