Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, ensuring parity for Windows and Linux users in most sections. However, in the 'Send requests' section, the PowerShell example is significantly more complex and uses advanced Windows-specific constructs (RunspacePool, PowerShell objects), while the Bash example uses standard Linux utilities (seq, xargs, curl). Additionally, instructions for opening a shell are phrased as 'Open a new bash shell' for Bash and 'Open a new command prompt and enter PowerShell' for PowerShell, subtly prioritizing Windows terminology. The PowerShell examples are always presented immediately after Bash, but never omitted, which can be interpreted as a mild 'windows_first' bias, especially given the complexity and length of the PowerShell examples compared to their Bash counterparts.
Recommendations
- Provide a simpler PowerShell example using basic loops and Invoke-WebRequest, if possible, to match the simplicity of the Bash example.
- Explicitly mention that Bash commands work in Linux, macOS, and Windows (via WSL or Git Bash), to clarify cross-platform applicability.
- Consider including a note about using Windows Subsystem for Linux (WSL) or Git Bash on Windows for users who prefer Bash commands.
- Ensure that instructions for opening shells are platform-neutral (e.g., 'Open a new terminal window' instead of 'command prompt').
- Where possible, offer parity in command complexity and explanation between Bash and PowerShell examples.
Create Pull Request