Vectors and Dot Products: The Math Under Every 3D Game
A vector is just an arrow with a direction and a length. The dot product is how code asks two arrows whether they're pointing the same way.
A vector is an arrow: it has a direction and a length, and that's the whole idea. In two dimensions, you can write one as a pair of numbers, like (3, 4) — "go 3 steps right, then 4 steps up" — and that pair is all the information the arrow needs. Add a third number for depth and you have the same idea in 3D, which is exactly how a game engine tracks which way something is facing or moving.
Vectors get used everywhere in games and graphics because "direction and distance" is such a common thing to need: which way is this character walking, how far is the camera from this object, which direction is this light shining from. Under the hood, a character's velocity, a surface's facing direction, and the path from a bullet to its target are all just vectors.
The dot product is the single most-used operation on vectors, and what it actually tells you is simple: how much two vectors point in the same direction. Multiply the matching coordinates of two vectors together and add up the results — that's the entire calculation. The number you get back is large and positive when the vectors point the same way, zero when they're perpendicular (pointing at exact right angles to each other), and negative when they point opposite directions.
That single number answers a question game and graphics code needs constantly: "is this surface facing the light, or away from it?" A game engine computes the dot product between a surface's facing direction and the direction toward a light source — a positive result means the surface is lit, a negative or near-zero result means it's facing away and should be dark. That one small calculation, repeated for every surface in a scene many times a second, is a real piece of why lighting in a 3D game looks convincing at all.
The dot product also shows up outside graphics anywhere "how similar are these two things" needs a number — search and recommendation systems represent items as vectors and use the same calculation to measure how alike they are, which is the same idea covered from the search-and-AI side in this site's "vector databases" article. Different application, identical arithmetic.