Cloud & IT: 30-Day Growth Guide

Главные выводы

• Thirty days of twenty to thirty minutes beat a frantic weekend, because each week's cloud theme builds on the last and gaps show up early.
• The cloud is rented computing delivered over the internet: you pay for servers, storage and software as you use them instead of owning them.
• Learn the four building blocks, compute, storage, networking and identity, and almost every cloud service becomes a variation you can recognise.
• Set a budget alert and turn on multi-factor sign-in before you create anything, because forgotten resources and stolen logins are the classic beginner disasters.
• When a week slips, shrink the daily task to ten minutes rather than skipping or doubling up, and move the exam date if you must.

Внутри этого бита

1. How the thirty days fit together

   This programme gives you four weeks, one theme per week and a small action every day. Week one is vocabulary and the big picture.

2. Week one: the cloud in plain words

   The cloud is other people's computers, rented over the internet. Huge buildings called data centres hold thousands of servers, and providers let you use slices of them by the minute or by the month.

3. Week two: four building blocks

   Almost every cloud service is a variation on four ideas. Compute is processing power, usually a virtual machine, which is a software computer carved out of a bigger physical one.

4. Week three: guard the door and the wallet

   Two beginner disasters are common enough to deserve a full week. The first is a surprise bill.

5. Week four: a small build and a practice exam

   The last week turns knowledge into proof. Early in the week, do one tiny project, ideally inside a free tier or a sandbox, which is a practice environment some training sites provide.

6. Measuring progress and rescuing a slipped week

   Track three things, not ten. First, minutes studied each day, written in a one-line log.