00. Philosophy::
// ORIENTATION— What do we believe, and what should we build?
What is philosophy?
Philosophy is difficult to define in a single sentence. Philosophers have understood its starting point and purpose in different ways.
Still, one common thread remains: philosophy is the act of stopping the assumptions we normally pass by and questioning them all the way down.
- Is this really true?
- What can we claim to know?
- What matters?
- What should we do?
- What does it mean to live well?
Philosophy does not attach a final answer to every question. It exposes the concepts and assumptions hidden inside a question, then checks what our judgments stand on.
One might say that Western philosophy repeatedly asked, “What is the essence of this?”, while Eastern philosophy spent more time asking, “How should we exist rightly in this world?” This is not a law dividing all of history, but one lens for looking at different habits of questioning.
What matters is the direction of the questions. Philosophy does not stop at explaining the phenomenon in front of us. It asks again what we should call real, what we should call true, and what kind of life and world we should consider good.
Extending the question into engineering
Engineers make choices every day.
We decide which problem to solve, choose the metric that defines success, and draw the line for automation. We trade performance against cost and convenience against privacy. A line of code, a database default, or an API permission can change someone’s behavior and opportunities.
Yet we usually call these decisions technical problems.
Philosophical questions extend into engineering right here. Before asking “How do we make this algorithm faster?”, we ask: “What are we making faster?”, “Who benefits from speed?”, and “Is this a problem worth solving in the first place?”
Engineering is the craft of changing the world. Philosophy is the craft of asking what should be changed, and why. Requirements, metrics, models, and systems always contain a worldview and a set of values.
Philosophy is engineering’s debugger
A good debugger does not immediately patch a broken line. First, it checks what went wrong, what behavior was expected, and whether that expectation was correct in the first place.
Philosophy works similarly. It looks for bugs deeper than the visible symptom:
- contradictions hidden in the requirements
- realities that a success metric fails to represent
- different people concealed behind the word “user”
- costs that quietly grow alongside efficiency
- the moment “we can” slips into “we should”
Technology without questions loses its destination, while questions without execution cannot change reality. Engineering and philosophy may appear to do different things, but together they become a way to test better questions in the real world.
Reading order
Starting with questions
What can we claim to know?
What should we do?
Humans inside systems
- What Does Free Will Have to Do with Design?
- Where Does Responsibility Live in Code?
- Can Humanity Be Automated?
The engineer’s attitude
What this section explores
This is not a study guide for a history-of-philosophy exam. It is a set of notes that brings old questions into today’s engineering situations.
- How far should AI and automation replace human judgment?
- What does free will have to do with system design?
- Do data and models describe reality, or remake it?
- If perfect systems are impossible, how should we choose our compromises?
- When does the responsibility of a toolmaker begin, and when does it end?
The goal is not to provide answers as quickly as possible, but to leave behind better questions.
Keep one thing in mind before reading the first essay:
Every system contains a philosophy its designer did not state aloud. These notes try to find that philosophy and choose it again, deliberately.