Skip to content
Dare Omotosho

New to cloud

Start at the beginning. In order.

Not a pile of links, a route. We'll go step by step, the latest resources are yours, and you don't need a background to begin. You need a direction.

The path

  1. 01

    Get your bearings

    What the cloud actually is, in plain language, and the handful of ideas everything else rests on.

  2. 02

    Build something small

    Stand up one real thing end to end. Confidence comes from shipping, not from reading.

  3. 03

    Learn to read the bill

    Cost is a design input, not an afterthought. See where the money goes before habits set.

  4. 04

    Think in risk

    Security sized to what you actually face. Start matching controls to real threats early.

  5. 05

    Connect it to the business

    The step almost no one teaches: every system you build is a decision the business is making.

Latest resources

The three newest answers from the library, no email wall. Take what's useful.

Community Questions

You learn it, then forget it, how do you make cloud concepts stick?

Keep reading, and don't miss the expert sessions where concepts are broken down. Use a variety of materials, follow good blog posts or YouTube videos for deeper explanations, and take notes during…

Read

Community Questions

What's the outlook for cloud computing in Africa?

With major providers like AWS and Microsoft opening offices and building data centers in parts of Africa, cloud adoption on the continent is rising and will keep growing in the years to come.

Read

Community Questions

Which AWS specialization should you bet on for the future?

All of the AWS tracks and specializations matter for future trends, whether AI/ML, IoT, serverless, or others. Rather than chasing the single hottest area, explore the tracks that align with your…

Read

Why cost

Because the bill is where engineering meets the business most directly, and where good judgment shows up first.

Why security

Because trust is the product. Right-sized security protects it without grinding delivery to a halt.

Why business-thinking

Because the engineers who rise are the ones who can say what a system is for, in the language leaders use.

In the age of AI

AI is very good at the tool. It's far weaker at the judgment.

Knowing which system to build, and why, given the business you're in, that's the part worth learning, and the part that lasts. Start there and you start ahead.

The best first step is the starter path.

Come with questions. Leave with a direction.