Extraneous load is mental effort imposed by how information or tasks are presented rather than by the task’s inherent complexity. It includes avoidable friction such as unclear errors, incomplete documentation, cryptic code, poor naming, and repetitive manual work. section 3.3.1
Reduce extraneous load by removing presentation and process friction around developer work:
- Automate onboarding, access configuration, and other repetitive setup instead of relying on checklists, help requests, or tribal knowledge. section 3.3.1
- Provide starter kits that generate a working repository and CI/CD pipeline so developers can focus on business logic. section 3.3.1
- Treat unresolved extraneous load as waste associated with technical debt, weak engineering leadership, or poor architecture, tooling, and process choices. section 3.3.2
Platform-supported application setup
When a developer joins a GitHub team, automated configuration grants the required access. A Python starter kit then generates a complete repository with CI/CD, allowing immediate business-logic work without requiring prior knowledge of Helm, Kubernetes, or OpenAPI specifications. section 3.3.1
Reducing extraneous load also supports faster feedback loops and sustained flow by removing delays from development tools, builds, tests, and environments. section 3.3.2
