Chapter 1: Baseball 101: More Than Just a Bat and a Ball
Imagine you’re holding a slice of pizza. Not just any slice—a delicious, triangle-shaped piece with a crispy crust. Now, look at a baseball field from above. See the similarity? The four bases—first, second, third, and home plate—form a diamond, which is really just a square turned on its point, making a perfect triangle if you connect home plate to second base. That’s your pizza slice! The pitcher’s mound is right in the middle, like the gooey cheese center. The outfield grass is the wide, crunchy crust stretching out behind the bases. Baseball’s playing field isn’t a boring rectangle like a football field or a soccer pitch; it’s a unique, symmetrical shape that’s been called “the diamond” for over 150 years. And just like every pizza has its own toppings and style, every baseball park has its own quirky dimensions—some outfield walls are really close (a “bandbox” park, easy for hitting home runs), while others are miles away (a “pitcher’s park,” where runs are rare). But before we get into the quirks, let’s start at the very beginning: what exactly *is* baseball, and why should you care about numbers in a game that seems to be about hitting, running, and catching?
At its heart, baseball is a simple game: two teams take turns trying to score runs. The team with the most runs after nine innings (or more, if there’s a tie) wins. An “inning” is like a chapter in a story—each team gets a chance to bat (hit the ball) and field (defend). The batter stands at home plate, holding a bat, trying to hit a ball the pitcher throws. If they hit it, they run counterclockwise around the bases—first, second, third, and back to home—scoring one run each time they successfully complete the circle. The fielders, spread across the diamond and outfield, try to catch the ball or get it to a base before the runner arrives. Three outs (when the defense gets three batters or runners “out”) end the team’s turn at bat. That’s the basic loop: pitch, hit, run, field, out. Repeat for nine chapters. Sounds straightforward, right? So where do numbers come in?
Numbers are the secret language of baseball. They’re not just the final score (like 5-3). They’re the *how* and the *why* behind every play. How fast did the pitcher throw? How far did the ball travel? How many times did the batter swing and miss? Baseball has always been a game of moments—a dramatic home run, a diving catch, a strikeout with the bases loaded. But to understand which moments matter most, which players are truly great, and what strategies actually work, you need to count them. You need data. And the very first data in baseball wasn’t collected by a supercomputer or a team of analysts in a dark room. It was written down with a pencil, in a humble little book called a scorebook.
Before we meet the man who started it all, let’s pretend we’re back in the 1840s, before professional leagues, before even standardized rules. Kids are playing stickball in empty lots, using a broom handle and a rubber ball. There are no uniforms, no stadiums, just informal games where everyone argues about the score. “We got three runs!” “No, we only got two!” How do you settle it? You write it down. You keep track. That’s the oldest form of baseball data: the scorecard, the tally, the “remember when” list. It’s human nature to count wins and losses, to track who hit the ball farthest, to brag about the best player. But turning those stories into systematic numbers—that was a revolutionary idea.
Enter our hero: Henry Chadwick. Picture a quiet, bespectacled man in the 1850s, sitting in a New York park watching a baseball game. He’s not just a fan; he’s a journalist and a statistician. He sees the game’s potential not just as entertainment, but as a *story*—a story that could be told with numbers. In 1858, he published the first baseball guide that included systematic statistics. He didn’t invent the game, but he gave it a memory. He created the box score—that grid you still see in newspapers today, with lines for each player’s at-bats, hits, runs, and errors. He invented the batting average (hits divided by at-bats), a simple but powerful way to judge a hitter’s success. He even came up with the earned run average (ERA) for pitchers, though that came later. Chadwick’s genius was in choosing *what* to count. He decided that the most important things were: hits, runs, outs (putouts), and errors. Those four categories became the foundation of baseball statistics for decades.
Why did this matter? Because numbers create objectivity. Before Chadwick, a player’s reputation was often based on hearsay or a single legendary game. “Old Hoss” Radbourn was great because people said so. But with a batting average of .300, you had a concrete measure. You could compare players from different teams, different cities, even different eras (with some caveats). Numbers let fans argue with facts instead of feelings. They let teams identify strengths and weaknesses. A manager could look at the scorebook and see, “Our leadoff hitter is only getting on base 30% of the time—maybe we need someone faster.” The humble scorebook became a strategic tool.
But Chadwick’s numbers were still *descriptive*. They told you *what happened*, not *why* it happened or *what would happen*. A batter gets a hit—great. But was it a weak infield single or a laser beam to the gap? A pitcher gives up three runs—bad. But were they all earned, or did his shortstop drop a pop fly? The early stats didn’t distinguish. They were like a pizza where you only know the total number of toppings, not whether you got pepperoni or mushrooms. That’s okay for a start, but as the game grew more sophisticated—with professional leagues, huge stadiums, and dedicated fans—people wanted to know more. They wanted to know *which* numbers truly predicted winning. They wanted to know *how* to build a better team, not just recount the past.
That curiosity is the seed of the data revolution we’ll explore in later chapters. But for now, in Chapter 1, we’re planting that seed. We’re going to walk onto the diamond, meet the nine positions (each with its own number and personality), and understand the basic flow of the game. Then we’ll open that old scorebook and see how Henry Chadwick’s simple columns of numbers started a chain reaction. Because every data revolution begins with someone deciding to write something down. Every algorithm, every advanced metric, every “sabermetric” (a term we’ll learn later) traces back to that moment when a fan said, “I’m going to count this.”
So, grab your glove and your pencil. We’re about to learn that baseball is more than just a bat and a ball. It’s a numbers game from the very first pitch. And you, my young statistician, are about to become fluent in its language.
---
The Diamond: Your Pizza Slice Field
Let’s take a closer look at that pizza slice. The pointy end is home plate, where the batter stands. The crust—the wide part—is the outfield. The two edges of the slice are the foul lines, which extend from home plate past first and third base all the way to the outfield fence. Any ball hit outside those lines is a foul ball—like tossing your pizza slice and having a topping fly off the edge. The area inside the lines, between home plate and the outfield fence, is fair territory—the yummy, edible part where all the action happens.
The infield is the smaller triangle inside the diamond, made of dirt or clay. It contains the four bases, which are soft, square cushions (traditionally made of rubber) anchored to the ground. They form a perfect 90-foot square (though the distance from home to second is about 127 feet, following the Pythagorean theorem: $a^2 + b^2 = c^2$, so $90^2 + 90^2 = 16200$, and $\sqrt{16200} \approx 127.3$). The pitcher’s mound is a raised circle of dirt in the center of the diamond, 60 feet 6 inches from home plate. That odd distance—60 feet 6 inches—was chosen in 1893 to give batters a fair chance against pitchers who were starting to throw fa