ai-assisted-learning

AI-Assisted Learning

Core Philosophy

AI raises the floor of developer competence — but the ceiling of senior expertise is defined by judgment, not syntax.

The biggest risk of AI-assisted learning is "Comprehension Debt" — shipping code you don't understand. The goal is to use AI as a force multiplier for your own thinking, not a replacement for it.

The rule: Use AI to understand faster, not to skip understanding.

---

The Socratic Method (Best for Deep Learning)

Instead of asking for answers, ask for dialogue:

Setup

I want to learn [topic] through dialogue. Do NOT give me solutions directly.
Instead:
- Ask me questions to guide my thinking
- Point out what I'm missing without filling it in
- Challenge my assumptions
- Only confirm when my reasoning is correct

My current understanding: [what you know]
My question: [what you want to understand]

Why It Works

Forces you to articulate your thinking → surfaces hidden gaps → builds durable mental models instead of just copying answers.

Socratic Learning Phases

Phase	What to Do	AI's Role
1. Debate	Ask "why does this work?"	Interrogate, challenge assumptions
2. Crystallize	Convert discussion into a spec	Confirm your architecture is sound
3. Anchor	Write tests before implementation	Define failure criteria
4. Implement	Build step by step	Guide, not do
5. Validate	Review your work	Find gaps, suggest improvements

---

Learning New Technologies

The AI Learning Loop

1. OVERVIEW: "Give me a 5-minute overview of [tech]. 
              What problem does it solve? When should I use it vs alternatives?"

2. MENTAL MODEL: "Explain the core concepts I need to understand 
                  before writing any code."

3. GUIDED BUILD: "Walk me through building [small practical example].
                  Explain each decision as we go."

4. CHALLENGE ME: "Quiz me on what I just learned. 
                  Ask about edge cases and gotchas."

5. APPLY: Build something real with the new tech.

6. REVIEW: "Review my implementation. What would a senior [X] 
            developer change and why?"