Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation demonstrates a Windows bias by consistently presenting Windows and PowerShell examples first and sometimes exclusively. Directory paths, terminal commands, and project setup instructions are shown using Windows conventions (e.g., C:\ paths, PowerShell commands), with no equivalent Linux/macOS shell examples. The Classic framework section is entirely Windows-specific, and cleanup instructions use PowerShell. While cross-platform NuGet packages are mentioned, practical usage and examples are Windows-centric, and Linux/macOS users are left to infer adaptations.
Recommendations
- Provide equivalent Linux/macOS shell examples (e.g., bash/zsh commands) alongside PowerShell commands for all steps, including directory creation, navigation, and cleanup.
- Show Linux/macOS directory paths (e.g., /home/user/msBuildDemo) in examples and instructions, not just Windows paths.
- Include explicit instructions for running MSBuild and dotnet CLI on Linux/macOS, including installation prerequisites and platform-specific notes.
- Add project file examples referencing Azure.Bicep.CommandLine.linux-x64 and Azure.Bicep.CommandLine.osx-x64, not just win-x64.
- Where Visual Studio is referenced, mention cross-platform alternatives (e.g., Visual Studio Code, JetBrains Rider) and clarify which steps are platform-agnostic.
- For cleanup, provide Linux/macOS equivalents (e.g., rm -rf ~/msBuildDemo) alongside Remove-Item PowerShell commands.
- Consider using neutral language and ordering (e.g., 'On Windows', 'On Linux', 'On macOS') rather than presenting Windows first or exclusively.
Create Pull Request