Free · AWS & Azure · Weekday mornings

Don't Know Jack

Daily cloud literacy. Ask better questions. Understand the answers.

Ask. Understand. Connect. Belong.

You're in. First concept arrives on the next weekday morning.

Free. Unsubscribe anytime. We only send the daily concept - no courses, no spam.

5
Minutes daily
No
Jargon unexplained
What you get

A weekly habit, not a course.

One story each week. A short daily practice. Puzzles when you want them.

Mon-Fri · Full Jack email

  • One cloud concept in plain language
  • Business consequence first - then the question
  • Four options so you can test what you understood
  • About five minutes on weekday mornings

Tuesday · Substack

  • The week's narrative - Selena, Bart, JJ, and Raja

Tue / Fri · LinkedIn

Sunday · Crossword

  • Selena's crossword - vocabulary from the week's story
What lands in your inbox

A real Full Jack sample

Bart speaks. You interpret. The technical answer is their job. Asking the right question is yours.

Security · Identity
Sample
The root user
The master key to the AWS account. One per account. Almost no restrictions. Should almost never be used, and often is.

Every AWS account has exactly one root user. Not one per team. Not one per department. One per account.

That identity can delete servers, wipe data, and close the account. AWS's own advice is to lock it away and almost never use it.

Here is what actually happens instead: it was set up years ago, two people have left, and nobody is sure who still has the password.

Five minutes. That's all it takes.
Today's question

Your engineering team says the root credentials were "set up when we first created the account." Nobody remembers who created it. That was four years ago. Two people have left since then.

What do you think Bart would push for first?
Words that matter
root credentials first
A
Create a new AWS account and start fresh
B
Find who holds root access and rotate those credentials immediately
C
Ask engineering to document all current users first
D
Enable billing alerts and wait for unusual activity
Who it's for

You nodded. So did everyone else.

Don't Know Jack is for business professionals who make or fund cloud decisions and want to ask the right questions.

📋
Project managers
Who write down technical terms to look up later, then brief teams with estimates that still feel arbitrary.
📊
Finance leads
Who approve cloud spend without a clear story for why this month costs what it costs.
🏢
Executives
Who signed the security strategy and want to ask sharper follow-ups in the next review.
🔍
Business analysts
Who work beside engineering daily and want to contribute, not only observe.
🎯
Product owners
Who need to understand why a "simple" feature still has a complicated deployment path.
💡
Anyone who nodded
Who searched a term at 11pm and got a four-page answer that assumed ten other terms.
How it works

Ask. Understand.
Connect. Belong.

Daily cloud literacy. Ask better questions. Understand the answers. Five minutes on weekdays. One concept.

01
Ask
The meeting question

Bart says something. You get the line that would have landed better if you had known what it meant before the room moved on.

02
Understand
What it actually means

Plain language. No jargon left unexplained. The concept, the business consequence, and why the words matter.

03
Connect
Cost, risk, decision

A short real-world note ties the idea to spend, security, or a choice your team already faces.

04
Belong
Stay in the conversation

Understanding the technical answer is their job. Asking the right questions is yours. Both matter. Only one requires a certification.

Ask. Understand. Connect. Belong.

You started not knowing Jack.

Five minutes on weekdays. One concept. Plain language. Free.

You're in. First concept arrives on the next weekday morning.

Free. Unsubscribe anytime.

You just knew a little more Jack than you did five minutes ago.
Five minutes. That's all it takes.