# Ci Cd
All Ci Cd notes →1 — Multi-Cloud Delivery
Covers designing delivery pipelines that build and deploy consistently across more than one cloud provider.
2 — Multi-Region Deployments
Covers coordinating deployments across multiple regions with staggered rollout, region-aware promotion, and blast-radius containment.
3 — Multi-Tenant Pipeline Platforms
Covers isolating tenants — teams, business units, or customers — sharing a single CI/CD platform without leaking access, quota, or blast radius.
4 — Platform Governance
Covers the organizational governance model — ownership, standards enforcement, exception handling — for a CI/CD platform used across an enterprise.
5 — Platform Cost Engineering
Covers attributing and optimizing the cost of build compute, runner fleets, artifact storage, and pipeline minutes at enterprise scale.
6 — Developer Experience
Covers measuring and improving the developer-facing experience of using the CI/CD platform — feedback latency, self-service, and cognitive load.
7 — GitHub Actions: Cost Optimization
Covers GitHub Actions minutes billing, storage costs, self-hosted runner economics, and concrete techniques to reduce CI spend.
# Internal Developer Platforms
All Internal Developer Platforms notes →1 — Multi-Team Platforms
Platform design considerations once dozens of independent teams, not one pilot team, depend on the same golden paths.
2 — Multi-Cloud IDPs
IDP design for organizations spanning multiple cloud providers, where the catalog and templates must abstract over provider differences.
3 — Multi-Region Platforms
Multi-region platform design: where the control plane lives relative to the regions it provisions into.
4 — Domain-Oriented Platforms
Domain-oriented platform structuring, where catalog ownership and golden paths are organized around business domains rather than one flat namespace.
5 — Platform Product Management
Product management discipline applied to an internal platform: roadmaps, prioritization, and internal stakeholder management.
6 — Scaling an Internal Developer Platform
What has to change structurally, team topology, catalog scale, template governance, as an IDP scales from one pilot team to the whole engineering org.
# Kubernetes Platform Engineering
All Kubernetes Platform Engineering notes →1 — Multi-Cluster Management
Operating a fleet of Kubernetes clusters as a single managed estate rather than a collection of independently administered clusters.
2 — Hybrid Cloud Platforms
Extending a Kubernetes platform across on-premises and public cloud environments with a consistent operating model.
3 — Multi-Cloud Kubernetes
Running Kubernetes platforms across multiple public cloud providers, and the portability tradeoffs that decision introduces.
4 — Platform Governance
The policies, guardrails, and approval workflows that keep a large-scale Kubernetes platform compliant and consistent across teams.
5 — Cost Optimization
Identifying and eliminating waste in cluster compute, storage, and networking spend without degrading platform reliability.
6 — Platform Standardization
Establishing shared conventions, templates, and golden paths across teams so platform capabilities compose predictably.
# Platform Engineering Fundamentals
All Platform Engineering Fundamentals notes →1 — Scaling Platform Teams
Covers organizational growth, multi-team collaboration, and platform ownership models as a platform org scales.
2 — Platform Governance
Covers platform standards, policies, compliance, and the decision frameworks that govern a platform at enterprise scale.
3 — Platform Maturity Models
Covers the crawl/walk/run maturity stages and continuous evolution of a platform engineering practice.
4 — Building a Platform Engineering Culture
Covers engineering excellence, shared responsibility, continuous learning, and building platform communities.