Informal English vs Technical English
Developers should learn and use informal English to enhance communication in collaborative environments, such as team chats, code reviews, and documentation aimed at general audiences, as it fosters approachability and reduces barriers meets developers should learn technical english to effectively collaborate in international teams, write clear code documentation, and communicate technical concepts to non-technical stakeholders. Here's our take.
Informal English
Developers should learn and use informal English to enhance communication in collaborative environments, such as team chats, code reviews, and documentation aimed at general audiences, as it fosters approachability and reduces barriers
Informal English
Nice PickDevelopers should learn and use informal English to enhance communication in collaborative environments, such as team chats, code reviews, and documentation aimed at general audiences, as it fosters approachability and reduces barriers
Pros
- +It is particularly useful for writing user-friendly documentation, engaging with communities on platforms like GitHub or Stack Overflow, and creating content for non-technical stakeholders, where formal language might seem distant or overly complex
- +Related to: technical-writing, communication-skills
Cons
- -Specific tradeoffs depend on your use case
Technical English
Developers should learn Technical English to effectively collaborate in international teams, write clear code documentation, and communicate technical concepts to non-technical stakeholders
Pros
- +It is crucial for roles involving technical writing, software documentation, API design, and participation in global open-source projects, as it reduces misunderstandings and improves the quality of technical deliverables
- +Related to: technical-writing, documentation
Cons
- -Specific tradeoffs depend on your use case
The Verdict
Use Informal English if: You want it is particularly useful for writing user-friendly documentation, engaging with communities on platforms like github or stack overflow, and creating content for non-technical stakeholders, where formal language might seem distant or overly complex and can live with specific tradeoffs depend on your use case.
Use Technical English if: You prioritize it is crucial for roles involving technical writing, software documentation, api design, and participation in global open-source projects, as it reduces misunderstandings and improves the quality of technical deliverables over what Informal English offers.
Developers should learn and use informal English to enhance communication in collaborative environments, such as team chats, code reviews, and documentation aimed at general audiences, as it fosters approachability and reduces barriers
Disagree with our pick? nice@nicepick.dev