Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation page demonstrates mild Windows bias. PowerShell is listed as a primary language for performance tuning, and Windows-centric tools like Visual Studio and Roslyn Analyzer are mentioned prominently, sometimes before cross-platform alternatives. Diagnostic tooling references focus on Application Insights and Visual Studio Code extensions, which, while cross-platform, are often associated with Windows workflows. There is a lack of explicit Linux or bash examples, and no mention of Linux-specific tooling or patterns.
Recommendations
- Include Linux/bash examples alongside PowerShell where relevant, especially in sections discussing performance and concurrency tuning.
- Mention cross-platform editors (e.g., VS Code, JetBrains Rider) equally with Visual Studio, and clarify Roslyn Analyzer usage on non-Windows platforms.
- Reference Linux-native diagnostic tools or CLI workflows (e.g., Azure CLI, log querying via shell) where appropriate.
- Add explicit statements or examples showing how to use Durable Functions tooling and diagnostics on Linux environments.
- Ensure that language and tool ordering does not implicitly prioritize Windows/PowerShell over Linux/bash or other cross-platform options.
Create Pull Request