Informal English vs Standard 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 and use standard english to create clear, error-free documentation, user interfaces, and communication with team members or clients, which reduces misunderstandings and enhances collaboration. 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
Standard English
Developers should learn and use Standard English to create clear, error-free documentation, user interfaces, and communication with team members or clients, which reduces misunderstandings and enhances collaboration
Pros
- +It is particularly important in global software projects where diverse teams rely on precise language for specifications, APIs, and support materials
- +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 Standard English if: You prioritize it is particularly important in global software projects where diverse teams rely on precise language for specifications, apis, and support materials 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