█
LastWrite
  • > Curriculum
  • > Pricing
  • > For Educators
  • > About
  • > Contact
Log InGet Started

Questions, concerns, bug reports, or suggestions? We read every message, write to us at [email protected].

More ways to reach us →
LastWrite

Structured computer science lessons for aspiring developers and security professionals.

[email protected]

(201) 785-7951

Mon–Fri, 9 AM–5 PM EST

Learn

  • Curriculum
  • Pricing

Company

  • About
  • For Educators & Schools
  • Contact Us

Legal

  • Terms of Service
  • Privacy Policy
© 2026 LastWrite. All rights reserved.
Curriculum/DevOps and Infrastructure/How to navigate the DevOps and Infrastructure tracks
5 minBeginner

How to navigate the DevOps and Infrastructure tracks

After this lesson, you will be able to: Understand how the LastWrite DevOps and Infrastructure track is organized so you can pick the right sub-track for your goals.

DevOps and Infrastructure is a parent track with 6 sub-tracks: Linux + CLI, Docker, Kubernetes, CI/CD, AWS, and Azure. Each sub-track can be taken independently; together they make a junior-to-mid DevOps / Platform / SRE / Cloud engineer.

This is a free introductory lesson. No purchase required.

Who this track is for

Students aiming at DevOps Engineer, Platform Engineer, Site Reliability Engineer (SRE), Infrastructure Engineer, or Cloud Engineer roles. Software Engineering teaches you to ship features; DevOps teaches you to run the systems those features ship to.

💡 Recommended path

1. Linux and the Command Line (Linux is the OS of the cloud; this is the foundation). 2. Docker (containers are how modern apps ship). 3. CI/CD (build the pipeline that deploys them). 4. Kubernetes (orchestrate containers at scale). 5. AWS or Azure (or both): one cloud platform deeply. Solo paths are valid too: a SRE candidate might go Linux → K8s → AWS; an automation-focused dev might stop at Linux + Docker + CI/CD.

What this track does NOT cover

It assumes Software Engineering basics (Git, testing, code review). Take the SE track first if those are new. It does not cover Terraform / Pulumi deeply (touched in AWS), Infrastructure-as-Code deserves its own future track. It does not cover security in depth, pair this track with the Cybersecurity track if you're targeting Security Engineer roles.

Back to DevOps and Infrastructure