Bias Analysis
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Bash and Azure PowerShell examples for all CLI steps, but PowerShell is featured equally and sometimes first, which can indicate a Windows bias. The prerequisites mention Bash and PowerShell, but clarify that Python, JavaScript, and Java samples require Bash, suggesting partial parity. However, PowerShell is presented as a first-class option throughout, and there are no explicit Linux-specific instructions or troubleshooting notes. The use of PowerShell may be confusing for Linux users, and there are no WSL or native Linux shell alternatives for PowerShell steps. The file editor recommendation (VS Code) is cross-platform, but no Linux-specific editors are mentioned.
Recommendations
- Clearly indicate when PowerShell is only supported on Windows, and recommend Bash for Linux/macOS users.
- Provide explicit Linux/macOS instructions for all steps, including environment setup and dependency installation.
- Add troubleshooting notes for Linux users, especially for PowerShell commands that may not work natively.
- Consider listing Bash examples before PowerShell to avoid implicit Windows-first bias.
- Mention Linux-native editors (e.g., Vim, Nano, Gedit) alongside VS Code.
- Clarify that Azure CLI commands are cross-platform and provide guidance for running them on Linux/macOS.
- Remove PowerShell examples from steps where Bash is required (e.g., Python, JavaScript, Java samples), or add a note explaining the limitation.
Create Pull Request