2.6.5 · D1Matrices & Determinants — Introduction

Foundations — Matrix multiplication — conditions, process, non-commutativity

2,319 words11 min readBack to topic

Before you can trust the parent page Matrix Multiplication, you must be able to read every squiggle it writes without pausing. This page builds each one from nothing, in an order where each idea leans only on the ones before it.


1. A number (scalar) — the smallest brick

Picture: one dot on a number line, or a "how much" label. Nothing has direction yet — a scalar only says how much, never which way.

Why the topic needs it: every entry inside a matrix is a scalar, and the final answers we compute (like ) are scalars. If you can add and multiply plain numbers, you already own the atoms of everything below.


2. A vector — an arrow with components

Figure — Matrix multiplication — conditions, process, non-commutativity

Look at the figure. The blue arrow is . Its shadow on the horizontal axis has length (the first component); its shadow on the vertical axis has length (the second component). The arrow is the pair of numbers — no more, no less.

Why the topic needs it: matrices act on vectors. The whole story " transforms into " only means something once you can picture as an arrow.


3. The dot product — the heartbeat of multiplication

The single computation the parent page repeats over and over is the dot product. Master this one thing and matrix multiplication becomes copy-paste.

Why "position by position, then add"? Because each pair answers one small question — "how much of ingredient , at price ?" — and the sum collects every ingredient's contribution into a single total. This is exactly the smoothie story in the parent's Feynman box.

Figure — Matrix multiplication — conditions, process, non-commutativity

Look at the figure. The top row (orange) and the side column (blue) are lined up. Each matched pair gets multiplied (the green links), and all products flow into one green box — the answer. Notice the row and column must be the same length, or some entries have no partner. That length-matching rule is the seed of the dimension rule in §6.


4. A matrix — a grid of scalars, read as rows and columns

Two ways to picture it, both useful:

  1. As a stack of rows — each row is a row vector, ready to be the left side of a dot product.
  2. As a line of columns — each column is a column vector, ready to be the right side of a dot product.

The parent page uses rows of and columns of , so keep both pictures live.


5. Subscripts and dimensions — the address system

For the above: (row 1, column 2) and (row 2, column 3).

Why the topic needs it: the parent's core formula (with the product from §4) is entirely subscript navigation. If is second nature, that formula reads like a sentence.


6. The compatibility condition — when can and even multiply?

The dot-product length rule from §3 grows directly into the rule that governs whole matrices.

Why exactly this rule? Every entry is the dot product of a row of (length , since has columns) with a column of (length , since has rows). From §3, a dot product needs equal lengths — so the row length and the column length must be the same . That is the whole condition, inherited from the dot product's partner-matching.


7. Sigma notation — "add up a pattern"

The parent's compact formula uses . It scares people only because it is unfamiliar; it means nothing more than "add these up."

Concretely, for :

Compare that to §3: it is literally the dot product of row of with column of , and it produces the entry of the product from §4. So is not new machinery — it is shorthand for the adding-up step you already did by hand.


8. The composition idea — why any of this exists

The parent's deepest claim is that means "do first, then ." That is the concept of composition, borrowed from Linear transformations.

Figure — Matrix multiplication — conditions, process, non-commutativity

Look at the figure. An arrow enters box , comes out changed, then enters box and comes out changed again. The dashed shortcut box labelled does both changes at once. Read the boxes right to left — that is why (written on the right) acts first.


Prerequisite map

The picture below shows which idea feeds which. If your reader's viewer does not render diagrams, here is the same thing in words: scalar is the atom; it builds both the vector and the matrix. Vector and matrix together give the dot product; the matrix also gives subscripts & dimensions, which grow into the compatibility condition and, with the dot product, into sigma notation. Separately, vector and matrix give composition. Both sigma notation and composition then feed the target topic, Matrix Multiplication.

Scalar - one number

Vector - arrow of scalars

Matrix - grid of scalars

Dot product - row times column

Subscripts and dimensions

Compatibility condition

Sigma notation - add a pattern

Composition - machines back to back

Matrix Multiplication

Notice two streams feed the topic: the mechanical stream (dot product → compatibility → sigma) tells you how to compute, and the conceptual stream (composition) tells you why the answer means anything.


Equipment checklist

Self-test: cover the right side and answer aloud.

I can read as an arrow
Yes — go 3 right, 2 up; the components are its axis-shadows.
The difference between a row vector and a column vector
A row is written flat ; a column is stacked vertically; the parent multiplies rows of by columns of .
How to take a dot product
Multiply the two lists position by position, then add all the products into one scalar; the lists must be the same length.
What points to
The scalar in row , column — row first, column second, both starting at 1.
What tells me
has 2 rows and 3 columns.
Who , , and are in
is the left factor (), the right factor () that acts first, and the product () built one entry at a time.
When can multiply
When is and is — the inner 's match; the product is ; otherwise undefined.
How to unpack
Let run to , form each product , and add them — it is exactly the dot product giving .
Why means " first, then "
Because is composition — — and we read the machines right to left.
Why in general
Swapping the order swaps which transformation runs first; a different pipeline gives a different result.

Connections