Most developers fall prey to common developer communication pitfalls. Here’s what not to do while communicating: (🧵)
1. Saying something is “easy” - Just because something is easy for you doesn’t mean it’s easy for everyone. When you’re explaining a concept to someone, try to avoid using the word “easy.”
2. Starting to design solutions on the fly
It’s important to take the time to really understand the problem before starting to design a solution. Otherwise, you may end up wasting time on a solution that doesn’t actually solve the problem.
It’s important to take the time to really understand the problem before starting to design a solution. Otherwise, you may end up wasting time on a solution that doesn’t actually solve the problem.
3. Interrupting people
Let people finish their thoughts before jumping in with your own ideas. Avoid talking too much - sometimes, less is more. It’s important to give people the opportunity to ask questions and contribute their own ideas.
Let people finish their thoughts before jumping in with your own ideas. Avoid talking too much - sometimes, less is more. It’s important to give people the opportunity to ask questions and contribute their own ideas.
4. Not listening enough - This is perhaps the most important communication skill for a web developer. You need to be able to listen carefully to understand what people are saying.
5. Making assumptions - Never assume that you know what someone is thinking or that they understand what you’re saying. This can lead to miscommunication and frustration on both sides.
That's a wrap!
If you enjoyed this thread:
1. Follow @codedamncom for more of these
2. RT the tweet below to share this thread with your audience
If you enjoyed this thread:
1. Follow @codedamncom for more of these
2. RT the tweet below to share this thread with your audience
Loading suggestions...