課程簡介

Module 1: Architecture Standards that Scale

Objective: Agree on a simple, shared set of architecture standards Principals can reference in daily decisions.

Topics

  • Architecture principles: what to standardize vs what teams decide
  • Decomposition basics: defining boundaries and ownership
  • Integration basics: API contracts, versioning, compatibility
  • Messaging overview: Kafka vs RabbitMQ, what to standardize
  • Data overview: ownership and source-of-truth thinking (Mongo + SQL Server)
  • Common architectural anti-patterns in high-scale systems
  • Lightweight decision documentation (ADR/RFC concept)

Module 2: Code Architecture in Large .NET Solutions

Objective: Align on practical guidance for code architecture decisions inside large solutions.

Topics

  • Structuring large .NET solutions: modules, layering, boundaries
  • Dependency direction and keeping architecture visible in code
  • Shared libraries: when they help vs when they create coupling
  • Integration boundaries in code: separation of concerns patterns
  • Code architecture “review lenses”: what to look for quickly
  • Managing exceptions without breaking consistency

Module 3: Design Reviews that Drive Decisions

Objective: Establish a consistent design review approach that produces decisions and shared understanding.

Topics

  • What makes a strong design review at Principal level
  • Review workflow: what gets reviewed and when
  • Review criteria: the few things that matter most
  • Facilitation: keeping senior discussions focused and productive
  • Decision closure: how to end debates and move forward
  • Capturing outcomes: decisions and follow-up actions
  • Practice review using a short case study (system-level)

Module 4: Influence Without Authority for Principals

Objective: Strengthen mentoring, feedback, and alignment habits with ICs.

Topics

  • Mentoring vs directing: coaching without taking ownership
  • Giving high-level technical feedback (clear, standards-based)
  • Driving alignment across ICs: practical techniques
  • Handling disagreement and resistance constructively
  • Simple conversation patterns and scripts Principals can reuse


 

最低要求

Participants bring 2–3 anonymized examples of recurring debates (system decomposition choices, integration approach, code structure rules). Any existing internal standards can be shared optionally.

 21 小時

客戶評論 (2)

課程分類