The Foundation Every
Cloud Engineer Needs.

File system navigation, permissions, text processing, and process management.

The operating system behind most servers and cloud—why it matters.

IP addresses, subnets, ports, DNS resolution, and basic network troubleshooting.

Version control basics, branching, merging, pull requests, and conflict resolution.

Branching model with main, develop, and supporting branches for features, releases, and hotfixes.

High-velocity branching strategy: single trunk, short-lived branches, and CI/CD-friendly workflows.

Request/response cycle, client-server model, HTTP methods, and basic web security.

The 12 principles every cloud app must follow: portability, reproducibility, and clean separation of config, code, and state.

What 12-Factor missed: API-first design, telemetry & observability, and security as architectural requirements.

Cloud native isn't just deploying to AWS. It's a philosophy: containers, microservices, immutable infrastructure, and declarative APIs.

Design the API contract before writing a single line of implementation. The principle behind Stripe, GitHub, and Twilio.

Werner Vogels' 7 laws for treating cost as a non-functional requirement — from day 1, not as an afterthought.

Toyota's manufacturing efficiency applied to cloud: eliminate waste, amplify learning, empower your team, and ship fast.

Six pillars for building secure, reliable, efficient, and cost-optimized systems — and the trade-offs between them.

How senior engineers approach architecture from scratch: requirements → scale estimation → components → bottlenecks → trade-offs.

Every architectural decision has costs and benefits. Learn the systematic process for making informed choices you can defend.

When to go serverless, when not to, cold starts, state management, and the real cost model behind functions-as-a-service.

The eight fallacies of distributed computing, CAP theorem in practice, replication, partitioning, and circuit breaker patterns.

The three pillars of observability, SLOs and error budgets, distributed tracing, and alerting that doesn't cry wolf.

Threat modeling with STRIDE, defense in depth, zero trust principles, secrets management, and supply chain security.

The carbon cost of compute, efficiency as sustainability, AWS carbon tools, and the Well-Architected Sustainability pillar.

Compile errors, CI pipelines, staging, and production monitoring — the four loops that separate fast teams from slow ones.

Fowler's quadrant, how debt compounds, when to take it deliberately, and the Boy Scout Rule for paying it back sustainably.