Skip to main content

EP4. Socratic Learning in Practice

💡 I Asked "Tell Me About Bloom's Taxonomy"—Here's What Happened​

"explain Bloom's Taxonomy in simple terms."

A ordinary question many of us ask. A typical ChatGPT or Claude might dump a long essay: "Bloom's Taxonomy is a framework proposed by Benjamin Bloom in 1956..." Focus fades in three seconds.

Cocrates answered differently. One or two sentences of essence—then a sharp mission out of nowhere.

🦉 Cocrates: "Bloom's taxonomy is famous for its six-level pyramid. Imagine a teacher designs a course that marches honestly from the bottom (Remember) to the top (Create). What's seriously wrong with that approach?"

No one-way information dump—questions back at you. How would you answer? Pause and think.

🗺️ Cocrates' Three-Step Learning Pipeline​

In this episode we'll walk through Cocrates' Learning pipeline using that real conversation.

  1. Education: Instead of an answer vending machine—flawed examples and missions that make you discover.
  2. Knowledge Capture: Don't copy walls of text—record into a knowledge base (KB) centered on gaps in your understanding.
  3. Reflection: Switch to interviewer mode and verify whether you really know.

🎓 Step 1. Education — Three Mind-Shifting Insights​

As I wrestled with Cocrates' question, assumptions I took for granted flipped pleasantly.

💡 Insight 1: The pyramid isn't 'lesson order'​

We often read the pyramid as master the base before the top. Bloom is talking about dependency structure, not a simple sequence.

In practice, the reverse often works better.

đź’» Assign: "Build your own programming website today! (Create)." Students hit walls, google syntax (Remember), and wrestle with why the code behaves this way (Understand).

A Pull strategy: a high-level task (Create) pulls lower-level knowledge (Remember, Understand). The myth that basics must be perfect before moving on breaks here.

💡 Insight 2: Not a 1D pyramid—a 2D matrix​

Cocrates dropped another twist: the 2001 revision is a two-dimensional matrix, not a single ladder.

RememberUnderstandApplyAnalyzeEvaluateCreate
Factual knowledge
Conceptual knowledge
Procedural knowledge
Metacognitive knowledge

Learning JavaScript's map splits across dimensions:

  • Factual: Memorize map syntax.
  • Conceptual: Grasp how the source array and callback relate.
  • Procedural: Type map in a real project.
  • Metacognitive: "I often mess up this binding when I use map"—notice your own habits.

Many of us only knew the 1D pyramid. Conversation peeled back one layer of ignorance.

💡 Insight 3: Push and Pull—a dance tuned to the learner​

The climax was harmonizing Push and Pull.

  • Push (sequential injection): Lower → higher stages step by step (good for beginners, cognitive overload).
  • Pull (mission-driven): Throw a high-level task; learn lower stages as needed (learners with basics, strong motivation).

Cocrates defaults to Pull—flawed missions that make you think. When you hit cognitive collapse, it switches kindly to Push and scaffolds concepts.

For Education's capstone, Cocrates assigned Create: "Design a 4-hour Git branching curriculum for new developers." Through that, I owned the ideas.

💾 Step 2. Knowledge Capture — Recording Gaps​

When I asked to summarize what I'd learned, Cocrates created kb/bloom-taxonomy.md.

The striking part: not a textbook summary. It centered on what I wrongly assumed (Gap).

đź“ť Wrong assumptions / Gaps

  • I thought Bloom was a simple 1D pyramid → the real model is a 2D matrix.
  • I thought teaching must go bottom-up → Pull is often more dynamic and effective.

Summaries bore you later. Records of past misconceptions restore the original aha at 200% intensity.

🧠 Step 3. Reflection — "You Sure You Know?"​

When I asked to verify my understanding, Cocrates became a tough interviewer.

Questions don't compromise. Pull strategy digs deep.

🦉 Cocrates: "Good. Map each session of your Git curriculum onto a cell in the 2D matrix."

I froze. Explaining concepts (Understand) vs. placing them precisely on the matrix (Analyze, Apply)—the gap was obvious.

After the interview, no hollow praise—a clear report card:

  • âś… Solid: What the pyramid really means; Push vs. Pull
  • ⚠️ Shaky: Applying the 2D matrix flawlessly in real instructional design

Finding those ⚠️ boundaries is Reflection's value. You grow when you know what you don't know.

📌 Key Takeaways​

  1. Education: Cocrates isn't an answer machine—it uses missions and Pull to provoke thought.
  2. Knowledge Capture: More powerful than summaries—record wrong assumptions (Gaps) and track ignorance.
  3. Reflection: Challenging questions draw the line between what you know and what you only think you know.

🎬 Coming Up Next​

You've tasted Socratic learning. Next: the crown of dev work—architecture-driven artifact generation.

We'll build a local store called jsondb from scratch with Cocrates. Watch how one line—"build this"—becomes three ADRs, one spec, and dozens of verification checks. The director's real battlefield—next episode. 🦉🚀

This series introduces the Cocrates Harness framework. Cocrates is an agent harness designed for Socratic dialogue so users keep agency and grow.