Separate the concepts, then connect them

Cloud learning often begins with the building blocks of an environment: compute, networking, storage and identity. DevOps learning concerns how development and operations work together, including repeatable delivery, feedback and recovery. The areas overlap, but a list of tools does not explain the relationship.

Use a small application as a reference. Draw where a request travels, where configuration lives and which component stores data. Mark the permissions each part needs.

Choose your immediate responsibility

If you cannot yet explain how an application reaches a database, infrastructure foundations may be the useful first step. If you can run the service but releases are manual and difficult to reproduce, a delivery workflow may be the better learning project.

Your current role matters. A developer, operator and analyst may need different starting points even when they use the same platform.

Practice locally before adding operational risk

A sample service can teach builds, tests, containers, configuration and health checks without production credentials. Introduce one failure and trace how you detect it. Then explain what a rollback would restore and what it would not.

Cloud subscriptions and hosted resources have their own permissions and costs. They should be an explicit choice, not a side effect of following a learning exercise.

Measure understanding through explanations

Try explaining a change from commit to running service. Identify the checks, approval points and observable signals. If a step is unclear, that is a useful target for the next exercise.

A mentorship inquiry can include a simple architecture diagram and a specific uncertainty. Avoid sharing credentials or internal infrastructure details before scope and permission are established.

Try this next

  • Draw a small service and its dependencies.
  • Identify one delivery step to make repeatable.
  • Describe how you would notice and recover from a failed release.