Non technical communications for devs
•Download as PPTX, PDF•
0 likes•32 views
A guide to the importance of communications
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
Non technical communications for devs
- 1. NON-TECHNICAL COMMUNICATION FOR DEVS MARCOS AMBROSI
- 2. Communication - the human connection - is the key to personal and career success.Paul J. Meyer
- 3. PROJECT MANAGER PRODUCT OWNER QA SALESOTHER DEVS FINAL USERS
- 4. GET INVOLVED
- 7. TRANSLATE
- 8. The method we use to populate the recycler view’s data source entered in an infinite loop which is producing an ANR. The app just crashed.
- 9. BE KIND
- 11. USE COMMUNICATION AS A WAY TO UNDERSTAND YOUR WORK
- 12. SUMMING UP 1. Get involved. 2. Be humble. 3. Make it simple. 4. Manage expectations.
- 13. THANK YOU
Editor's Notes
- - No matter what field you are in, communication is king. - As devs we feel proud of the knowledge we’ve gained and feel an uncontrollably need to show it off. - Non-tech communication should be part of that set of skills we take credit for. NEXT SLIDE Why communication makes us better devs?
- Being a dev involves dealing with complex abstract problems that in most cases are difficult to put into human-readable words.
- - Get familiar with your team. - If you feel unsure whether someone has a tech background or not, just ask.
- Assume you can always learn from anyone in the team. Don’t assume you’re right from the get-go.
- - Even when you are not using tech terminology, you’re still putting complex issues on the table. - Help others keep focus on what the issue is about (avoid acronyms or buzzwords).
- Make a list of the technical terms you use the most and translate them into a word or phrase that’s easier to understand. Library = Tool, Technology
- Not everyone has to know about all subjects so patience and kindness are key to getting your point across. Always choose encouragement over criticism.
- Be clear when you are unsure about whatever you need to do. Don’t commit yourself to a date you’re not confident you will deliver to. Try to anticipate to notify any complication you might foresee.
- - Whenever we talk to a teammate about a technical issue we or describe how a system works…