Skip to content

How I Learn

The method behind these notes — and why they look the way they do.

The Problem with Most Study Notes

Most AWS notes are either:

  • Too shallow — service lists with no mental model behind them
  • Too long — copied from docs, impossible to revisit quickly
  • Not connected — individual facts with no architecture thinking

Notes like that fail at recall. You read them once, remember 30%, and never go back.

The Compression Method

Every note here follows the same structure:

  1. Ultra-short summary — what is this really about, in 3–5 sentences
  2. Key concepts — terms and definitions, 1–2 lines each, no filler
  3. Mental model — the core idea as a flow: Service A → does X → produces Y
  4. AWS context — which services, which real scenarios, SAA-style thinking
  5. Step-by-step (where relevant) — workflow extracted as clean bullet steps
  6. 30-second takeaway — the compressed pocket version
  7. Self-quiz — scenario-style questions focused on tricky distinctions

The goal: read a note once, understand the structure of the idea, and be able to recall the pattern — not individual facts.

Why This Works (For Me)

My brain stores patterns, not isolated details. So instead of memorising "S3 stores objects" I build:

Data that doesn't change often, needs global access, no fixed size
→ Object storage
→ S3
→ Bucket + Key + Value model
→ Versioning, lifecycle policies, cross-region replication
→ SAA: "durable, scalable, cheap" = S3

Once the pattern is there, everything else slots in around it.

The Learning Workflow

Step Action
1 Define what I'm learning exactly
2 Strip to the smallest building block
3 Understand the layer underneath it
4 Add one layer of complexity
5 Identify the pattern — what category does this belong to?
6 Ground it in 2–3 real examples
7 Teach it back in my own words
8 Connect it across domains (networking → VPC → security groups → IAM)
9 Iterate — revisit, refine, repeat

Learning Mirrors Bodybuilding

The same principles apply:

Bodybuilding Learning
Progressive overload Increasing conceptual load
Volume Repetition and practice
Recovery Spacing + rest between topics
Nutrition Quality inputs (labs, diagrams, real scenarios)
Periodisation Focused blocks (SAA → CDK → Security → etc.)

Don't cram. Build progressively. The compound effect over months is enormous.

How I Handle Learning at Work

The high-ROI combo:

Agentic content (compliance skim) → Lab (hands-on mastery) → SAA scenario (reasoning)
  • Passive content (videos, docs) → skim for pattern, don't try to memorise
  • Labs → this is where real understanding happens
  • Scenario questions → builds architecture intuition, not just fact recall

What These Notes Are Not

  • Not a replacement for labs (do the lab, then read the note)
  • Not a certification cheat sheet
  • Not complete — they grow as I learn

They're a working system, not a finished product.