Majk Majk ·
1. Welcome 2. Organise Your Downloads 3. The CODER Framework 4. CODER — The Moves 5. O — Organise 6. Interpretive Organisation 7. C — Compute Overview 8. Batch Operation 9. Map / Reduce 10. D — Display Overview 11. Corpus to Dashboard 12. E — Engineer Overview 13. Living Document 14. R — Reason Overview ✓ 15. Tradeoff Analysis 16. Generate Failure Scenarios 17. The Cross-Reference 18. The Stress Test 19. Course Complete 20. Scenario Catalog 21. Resume Screening 22. Performance Review Draft

You've learned to engineer. Now let's reason.

Every tutorial so far has had a right answer you could check. You ran a batch operation and got organised files. You built a dashboard and saw the data. You set up a living document and watched it update. The output was always verifiable.

Reasoning is different. There's no output file to verify. The value is in the thinking process itself — the AI holding your actual constraints, weighing the tradeoffs, and giving you judgment you couldn't easily get from a spreadsheet or a search engine.

You're not asking for information. You're asking for thinking applied to your specific situation.


Where you are

CODER

C Compute — extract, transform, and calculate across files and data ✓ done
O Organise — impose meaningful structure on files, folders, and data ✓ done
D Display — build dashboards, galleries, visual reports, websites ✓ done
E Engineer — create pipelines, automations, and repeatable workflows ✓ done
R Reason — analysis, synthesis, evaluation, judgment ← you're here

R — Reason

The first four letters are about transformation — you give the AI data, files, or a folder, and it produces something new. Reasoning asks for something harder: judgment applied to a situation where there's no clean formula.

The difference isn't intelligence — it's the type of problem. Reasoning problems have competing priorities, uncertain information, and tradeoffs that depend on your specific context. The AI's job isn't to run a calculation. It's to think alongside you.

  • Two job offers, both attractive, very different shapes — which one fits your actual life right now?
  • A plan you're about to execute — generate every failure scenario before you commit
  • A team problem that keeps recurring — build a hypothesis list, rank it, and test the most likely cause
  • A decision you've already made — challenge your own reasoning before you act on it

In each case, the key move is the same: you give the AI your actual constraints, your real tradeoffs, and your specific situation — not a generic version of the problem. The more specific you are, the more useful the thinking it returns.


What's next

Four reasoning patterns. Start with the Tradeoff Analysis — the canonical Reasoning move. You have two options, both reasonable, and the right answer depends entirely on which constraints matter most to you.

← Back Next →