欢迎大家提Issue反馈问题或建议,建设推理王国!
Skip to content

Chapter 17: The Reasoning Scientist's Toolbox

A Letter from Mr. Pallas's Cat
Dear Piglet and Little Seal:

The kapok blossoms are beginning to fall. Red petals carpet the paths of Kangle Garden like a soft rug. Spring is passing, and our journey is nearing its end.

This is the second letter of Part 4. In the last letter, we talked about "what is true reasoning." Today, I want to take inventory of the toolbox together with you.

We've spent an entire book filling this box with tools. Now it's time to open it and see what we have.

But remember: tools are dead; people are alive. A hammer doesn't drive nails by itself; an algorithm doesn't solve problems by itself.

What truly matters is not what's in the toolbox, but how you use it — and for whom you use it.

Don't rush. Let's take it slow. The tea is still warm.


Reviewing the Journey

Piglet, do you remember how we started?

Chapter 1: we talked about everyday reasoning — how to plan routes, how to allocate time, how to make choices. Back then you said: "Isn't reasoning just thinking about problems? What's so special about it?"

Little Seal, you gently added at the time: "But there are many ways to 'think about problems.' Some rely on intuition, some make lists, some draw diagrams."

Yes. Back then we didn't realize that this simple observation would lead to such a rich world.

Later, we encountered algorithmic thinking — breaking big problems into small ones and solving them step by step. Like building with blocks, like following a recipe.

Still later, we encountered neural network thinking — letting machines learn from data, finding hidden patterns. Like teaching a child to recognize cats — not by telling them "cats have whiskers and tails," but by showing them many pictures of cats.

Now, standing at the end of the journey, we look back.

What have we learned?

Core Concept: Integrating Three Modes of Thinking

Let me summarize our toolbox in the simplest way:

1. Algorithmic Thinking: The Art of Certainty

Piglet, this is your favorite. Like a Lego instruction manual — step by step, precise and seamless.

Key tools:

  • Problem decomposition: how many steps to put an elephant in a fridge? Open the door, put it in, close the door.
  • Abstract modeling: ignore details, capture the essence. The map is not the territory, but it helps you find your way.
  • Recursive thinking: Russian nesting dolls. The method for solving a big problem is to first solve smaller problems using the same method.
  • Greedy choice: at each step, pick what looks best right now. Not necessarily globally optimal, but often good enough.

When to use? When the problem has clear rules and deterministic solutions. Like sorting, searching, route planning.

2. Neural Network Thinking: The Wisdom of Probability

Little Seal, this is what you've studied deeply. Like cultivating intuition — not through rules, but through experience.

Key tools:

  • Representation learning: let the machine discover useful features on its own. Don't tell it "cats have pointed ears" — let it learn from pixels.
  • Gradient descent: descend along the steepest direction. Error is not failure; it's the ladder of progress.
  • Attention mechanisms: in this noisy world, where should we look? Learn to focus.
  • Transformer stacking: simple components, through careful organization, give rise to complex capabilities.

When to use? When the problem is fuzzy, complex, and lacks clear rules. Like image recognition, natural language, recommendation systems.

3. Reasoning Thinking: The Depth of Understanding

This is what we explored last. Like a philosopher questioning, like a scientist verifying.

Key tools:

  • Logical reasoning: if P then Q; P holds; therefore Q holds. A rigorous chain.
  • Causal inference: not just correlation, but causation. Rain causes the ground to be wet, not the other way around.
  • Bayesian updating: revise old beliefs with new evidence. The humble learner.
  • Metacognition: thinking about one's own thinking. I know what I know, and I know what I don't know.

When to use? When understanding, explanation, and proof are needed. Like scientific discovery, legal argumentation, medical diagnosis.

Key Takeaways: How to Choose Tools?

Piglet, you asked last time: "Facing a new problem, should I use algorithms or neural networks?"

Good question. Let me share some insights:

Problem Decomposition Strategy

Step 1: Understand the nature of the problem

  • Does it have clear rules? (Chess rules are clear; conversation rules are fuzzy)
  • Is there abundant data? (Translation has parallel corpora; creative writing doesn't)
  • Does it need explainability? (Medical diagnosis needs explanation; recommendation systems can be black boxes)

Step 2: Choose the right mode of thinking

  • Certainty + clear rules → algorithmic thinking
  • Fuzziness + abundant data → neural network thinking
  • Need for understanding + explanation → reasoning thinking

Step 3: Combine them Often, the best solution is a combination. For example:

  • Use algorithms for preprocessing (cleaning data)
  • Use neural networks for core processing (learning patterns)
  • Use reasoning for postprocessing (explaining results)

Model Selection Principles

Little Seal, you've studied many models. Let me summarize a few simple principles:

  1. Simplicity principle: if a simple model works, don't use a complex one. Occam's razor.
  2. Explainability principle: unless necessary, don't use black-box models. Understanding matters more than accuracy.
  3. Robustness principle: the model should perform stably across situations, not just perfectly on the training set.
  4. Ethical principle: consider the social impact of the model. Technology is a tool, not an end.

The Wisdom of Decoupling

This is one of the most important wisdoms: don't solve problems bundled together.

Take autonomous driving:

  • Don't use one model for object detection, path planning, and decision control simultaneously
  • Instead: detection module → planning module → control module
  • Each module is relatively independent, easy to debug, improve, and replace

The wisdom of decoupling: complex systems are not tangled messes, but organic combinations of clear modules.

Orthogonal Strategies for High-Dimensional Data

Little Seal, you've studied linear algebra. Remember "orthogonal"? Perpendicular, independent, mutually non-interfering.

In thinking, orthogonality means:

  • Different dimensions of thought are mutually independent
  • Changing one dimension doesn't affect others
  • Each dimension can be optimized independently

For example, designing a recommendation system:

  • Accuracy is one dimension
  • Diversity is another
  • Novelty is yet another
  • They can be optimized separately, then combined

The wisdom of orthogonality: in complex spaces, advancing along independent directions is more effective than struggling in entanglement.


Reflection Question: Facing a New Problem, How Would You Choose?

Piglet, Little Seal:

Imagine this problem: helping elderly people remember to take their daily medication.

How would you design a solution?

Let me guess your thought processes:

Piglet might think:

  1. Problem decomposition: reminder → confirmation → recording
  2. Algorithm design: scheduled reminders, button confirmation, database logging
  3. Hardware choice: smart pillbox? Mobile app? Voice assistant?

Little Seal might think:

  1. Historical research: why do elderly people forget medication? Memory decline? Habit issues?
  2. Theoretical framework: behavioral psychology? Habit formation theory?
  3. Ethical considerations: privacy issues? Autonomy concerns?

And I would suggest: combine your thinking.

Algorithmic part (Piglet's strength):

  • Design simple reminder logic
  • Design an easy-to-use interface
  • Design reliable data storage

Understanding part (Little Seal's strength):

  • Research the actual needs of elderly people
  • Consider usage contexts (at home? In a nursing home?)
  • Design interactions that respect autonomy

Neural network part (if needed):

  • If there's enough data, learn each person's medication patterns
  • Predict time points when they're likely to forget
  • Personalize reminder strategies

Most importantly: stay humble. Build a prototype first, test it, collect feedback, iterate and improve.


The Deep Structure of the Toolbox

Let me share a deeper insight. Our toolbox actually has three layers:

Layer 1: Concrete Tools

  • Quicksort algorithm
  • Backpropagation formula
  • Attention mechanism
  • Bayes' theorem

These are skills. Once learned, they solve specific problems.

Layer 2: Thinking Patterns

  • Decompositional thinking
  • Probabilistic thinking
  • Causal thinking
  • Systems thinking

These are methods. Once mastered, they handle a class of problems.

Layer 3: Meta-Abilities

  • Learning ability: how to learn new tools?
  • Selection ability: how to choose the right tool?
  • Creation ability: how to create new tools?
  • Critical ability: how to evaluate tools?

These are wisdom. Once possessed, they face any unknown problem.

This book aims to give you not just Layer 1 skills, but Layer 3 wisdom.

To You: Setting Out with Your Toolbox

Piglet, Little Seal:

The kapok blossoms have fallen, but the flame trees are about to bloom. On the Sun Yat-sen University campus, different flowers always follow one another.

Our journey is ending, but your learning has only just begun.

This toolbox now belongs to you.

But remember: tools are dead; people are alive. A hammer doesn't drive nails by itself; an algorithm doesn't solve problems by itself.

What truly matters is not what's in the toolbox, but how you use it.

A few final suggestions:

  1. Stay curious: curious about the world, curious about problems, curious about yourself.
  2. Stay humble: know your limitations, be willing to learn, be willing to change.
  3. Stay connected: communicate with others, dialogue with different fields, interact with the world.
  4. Stay creative: not just use tools, but improve them, create new ones.

Most importantly: enjoy the pleasure of thinking.

Reasoning is not drudgery, but a game of exploring the world. Every problem is a puzzle; every solution is a discovery.

We'll take it slow. Understanding is what matters most.

I look forward to hearing the stories you create with this toolbox.

Yours, Mr. Pallas's Cat Black Stone House, Sun Yat-sen University In the season when kapok falls and flame trees await bloom


Mr. Pallas's Cat's Reflection Questions

Hands-On Exploration (for Piglet)

  1. Toolbox inventory: list all the "tools" you've learned from this book. Which are you best at? Which need more practice?
  2. Problem-solving diary: pick a recent problem and record how you used your toolbox to solve it. Which tools did you use? How did you combine them?
  3. Tool creation: try creating a new "thinking tool." It could be a combination of existing tools or an entirely new idea.

Historical Investigation (for Little Seal)

  1. Tool evolution: choose one thinking tool (e.g., "decompositional thinking") and research its historical evolution. Who first proposed it? How did it develop?
  2. Cross-cultural comparison: compare thinking tools across cultures. What differs between East and West? Between ancient and modern?
  3. Future tool prediction: based on historical trends, predict what new thinking tools might emerge. What might they look like?

Integrated Reflection

  1. The limits of tools: every tool has limits. What are the limits of algorithmic thinking? Of neural network thinking? Of reasoning thinking?
  2. The ethics of tools: can thinking tools be misused? For instance, algorithmic thinking may lead to oversimplification; neural network thinking may lead to black-box decisions. How to guard against this?
  3. Educational reflection: does the current education system teach students enough thinking tools? How should it be improved?
  4. Personal growth: review your learning journey. Which thinking tools changed how you see the world? What new tools do you hope to master in the future?

Piglet's note: The Professor's letter made me want to organize my toolbox. I found I'm best at algorithmic thinking, but reasoning thinking needs strengthening. From today, I'll ask "why" more, not just "how."

Little Seal's note: The Professor mentioned "meta-abilities." This reminds me that the most important thing is not knowing many tools, but knowing how to learn new tools. In this era of rapid change, the ability to learn may be the most important ability of all.

Mr. Pallas's Cat's closing words: The true value of a toolbox lies not in how full it is, but in how open it is. Willing to take in new tools, willing to set aside old ones, willing to share good ones — such a toolbox only grows richer and more useful with time.