Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation demonstrates a Windows-first bias, with Windows tools and workflows (such as Visual Studio, PowerShell, and Windows command prompts) being mentioned before or more prominently than Linux equivalents. In several sections, Windows-specific instructions and tools are detailed, while Linux alternatives are either briefly referenced, deferred to external links, or presented after the Windows instructions. Some programming language pivots (notably C and Python) assume a Windows-based machine by default. The use of PowerShell for key derivation is highlighted, and Visual Studio is the primary IDE discussed for C development, with Linux instructions relegated to linked SDK documentation. While Linux examples are present (notably for device key derivation and some SDK usage), they are less detailed or less immediately accessible.
Recommendations
- Present Linux and Windows instructions with equal prominence and in parallel, rather than defaulting to Windows-first.
- For each programming language, provide explicit, step-by-step Linux setup and usage instructions alongside Windows instructions, rather than referring users to external SDK documentation for Linux.
- Include Linux-native tools (e.g., gcc, make, VS Code, or CLion) as alternatives to Visual Studio for C/C++ development.
- Where PowerShell is used for Windows, provide a Bash or Python script alternative for Linux/macOS in the same section.
- Avoid language such as 'This tutorial is oriented toward a Windows-based workstation'—instead, state that the tutorial supports both Windows and Linux, and provide side-by-side instructions.
- Ensure all command-line examples are shown for both Windows (cmd/PowerShell) and Linux (bash), especially for environment variable setting and running SDK samples.
- Where possible, provide screenshots or terminal output from both Windows and Linux environments.
Create Pull Request