What does effective communication for developers look like? @iMeluny has some thoughts. A thread 
Show this thread
-
How much context do you need to provide? Keep instructions concise, but not curt. Messages that are too short, and without sufficient detail, can be easily misinterpreted.
Show this thread
Draft your message before reaching out. Don’t drop a casual “hey!’ or “we need to talk” message without additional information. Research shows that this ambiguity can stress people out.
-
-
Pro Tip: Regardless of what channel you choose, explain why you chose it. “I’d like to set up a video call so we can talk this through quickly,” or “I’m reaching out over email so you can respond at your convenience.”
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
