Cloud technology explained in plain language for people who have better things to do than get certified.
No credit card. No certification. Five minutes a day.
You're in. First concept arrives tomorrow morning. 🌿
Understanding concepts before solutions. Because everyone's fix is different but the concepts are universal.
One cloud concept explained in plain language. Real analogies. Business consequences first. Zero jargon left unexplained. Arrives in your inbox before your first meeting.
Four options. Intent words highlighted so you know what the question is actually testing. Submit your answer and find out immediately if you knew Jack.
Not just what is correct. Why every wrong answer is wrong, and the specific condition under which each one would have been right. The real learning lives here.
This is what lands in your inbox every morning and afternoon. Plain language. Dry humour. Business consequences first.
Every AWS account has exactly one root user. One. Not one per team. Not one per department. One per account.
The root user can do absolutely everything inside that account. Delete every server. Wipe every database. Cancel the account entirely. No exceptions. No restrictions. No permissions required.
AWS's own advice is to create it, lock it in a metaphorical drawer, and almost never use it. Here's what actually happens instead.
Your engineering team mentions the root user credentials were "set up when we first created the account." Nobody can remember who created the account. That was four years ago. Two people have left since then.
Don't Know Jack is for the professionals who sit alongside engineering teams and have been waiting for someone to explain this properly.
No certification required. No engineering degree assumed. Just cloud, finally making sense.
Five minutes a day. One concept. Plain language. No jargon left unexplained. Starting tomorrow morning.
You're in. See you tomorrow morning. 🌿