Senior Engineer · Interdisciplinary Growth Map
Filter By Phase:
Phase 1Foundation
Phase 2Integration
Phase 3Mastery
| Discipline | Phase | Priority | Duration | Format | Resource | Application | |
|---|---|---|---|---|---|---|---|
| ▶ | Cognitive Psychology | 1 · Foundation | High | 4–6 weeks | Book + Practice | Thinking, Fast and Slow — Kahneman | API design, code review, debugging discipline |
| ▶ | Systems Thinking | 1 · Foundation | High | 6–8 weeks | Book + Diagramming | Thinking in Systems — Donella Meadows | Incident analysis, distributed system design, capacity planning |
| ▶ | Bayesian Reasoning & Decision Theory | 2 · Integration | High | 4–6 weeks | Book + Daily Exercise | The Art of Doing Science and Engineering — Hamming | Debugging, incident response, build-vs-buy decisions, risk assessment |
| ▶ | Organizational Behavior & Sociotechnical Systems | 2 · Integration | High | 6–8 weeks | Book + Retrospectives | Accelerate — Forsgren, Humble, Kim | Team design, incident culture, reliability engineering, technical debt strategy |
| ▶ | Philosophy of Science & Epistemology | 2 · Integration | Medium | 4–5 weeks | Book + Applied Writing | Conjectures and Refutations — Popper | A/B testing, post-mortems, technical strategy, experimentation culture |
| ▶ | Information Theory | 3 · Mastery | Medium | 5–7 weeks | Paper + Applied Reading | A Mathematical Theory of Communication — Shannon (1948 paper) | Observability design, protocol design, API surface area, compression systems |
| ▶ | Economics & Incentive Design | 3 · Mastery | Medium | 4–6 weeks | Book + Org Analysis | Governing the Commons — Ostrom | Tech debt strategy, shared platform governance, team structure design, on-call design |
CLICK ANY ROW TO EXPAND CONCEPTS & ACTIVITIES
7 of 7 disciplines shown