adjacent-disciplines

Files (1)

• SKILL.md

SKILL.md (first lines)

# Adjacent Disciplines

Cross-domain knowledge for solving engineering problems that span traditional boundaries.

## When to use

- A problem can't be solved with pure software engineering
- You need insights from related fields (HCI, cognitive psych, game theory)
- Designing systems that interact with humans or complex organizations

## Instructions

1. **Identify the cross-disciplinary need** — what other fields are relevant?
2. **Apply relevant frameworks**:
   - **Systems engineering**: V-model, tradeoff analysis, requirements traceability
   - **HCI**: Fitts's law, Norman's design principles, learnability vs efficiency
   - **Cognitive psychology**: mental models, cognitive load, decision fatigue
   - **Game theory**: Nash equilibrium, prisoner's dilemma, mechanism design
   - **Control theory**: feedback loops, PID controllers, stability analysis
   - **Organizational behavior**: Conway's law, team topology, incentive design
3. **Synthesize across fields** — combine insights to produce novel solutions

## Key references

- **HCI**: Don Norman's "Design of Everyday Things" — visibility, feedback, affordances, constraints, mapping, consistency
- **Systems thinking**: Peter Senge's five disciplines — personal mastery, mental models, shared vision, team learning, systems thinking
- **Game theory**: Axelrod's cooperation strategies — tit-for-tat, forgiveness, reciprocity

## Anti-patterns

- Superficial application (using a term without understanding its substance)
- Ignoring domain-specific constraints (what works in one field may not work in another)
- Overcomplicating (use the simplest model that captures the relevant dynamics)

From Mr-Wolv/Skill_Playground_Bakr101_2026, MIT.

More from Mr-Wolv/Skill_Playground_Bakr101_2026