About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
windows_tools
⚠️
powershell_heavy
Summary:
The documentation demonstrates a mild Windows bias in several areas: Windows terminology ("command prompt") is used alongside or before cross-platform terms ("terminal"), and Windows-specific recommendations are made (e.g., suggesting remote build when developing on Windows, discouraging local builds on Windows). The documentation refers to the 'command prompt' and 'Visual Studio Code' as primary development environments, which are more common on Windows. There is also a subtle bias in the order of mentioning Windows-specific tools or patterns before their Linux equivalents, and in some cases, the documentation assumes a Windows context before clarifying Linux is required for hosting. However, Linux support is well-documented, and many examples are cross-platform.
Recommendations:
- Use fully cross-platform terminology throughout (e.g., always say 'terminal' instead of 'command prompt').
- When listing development environments or tools, avoid putting Windows-specific options first or exclusively; instead, clarify cross-platform support and order neutrally.
- Where recommendations are made (e.g., for remote vs. local build), explain the rationale for all platforms, not just Windows.
- Explicitly provide Linux/macOS shell examples (e.g., bash/zsh) alongside any Windows-specific instructions, if any.
- Clarify that Visual Studio Code is cross-platform, and suggest other editors (e.g., Vim, Emacs, PyCharm) where appropriate.
- Avoid language like 'Use remote build when you're developing Python apps on Windows' without also explaining the implications for Linux/macOS users.
- Ensure that all CLI commands are shown in a cross-platform way (e.g., use $ for shell prompts, not C:\> or cmd).
Create pull request