Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation consistently provides examples for Azure CLI and Azure PowerShell, but omits Linux-native equivalents (e.g., Bash scripts, shell patterns) and does not mention Linux-specific tooling or editors. Visual Studio and Visual Studio Code are referenced as primary editors, both of which are Windows-centric (VS is Windows-only, VS Code is cross-platform but presented without mention of Linux). PowerShell examples are given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. There are no explicit Linux shell examples, and no mention of Linux package managers or shell environments.
Recommendations
- Add Bash shell examples alongside Azure CLI, demonstrating usage in a typical Linux terminal.
- Explicitly mention that Azure CLI commands work cross-platform, and provide Linux-specific instructions for installation and usage.
- Include references to Linux-native editors (e.g., Vim, Emacs) or at least acknowledge their use for Bicep development.
- Clarify that Visual Studio Code is available on Linux and macOS, and provide installation links for those platforms.
- Reduce emphasis on PowerShell, or clarify its cross-platform availability, and provide parity for Linux shell environments.
- Where file paths are referenced, use both Windows (\) and Linux (/) path conventions in examples.
Create Pull Request