Okay, folks, let’s dive into my little project from today – tracking player stats for the Sacramento Kings vs. New Orleans Pelicans game. I’m no pro analyst, but I love digging into the numbers, so I figured, why not record it all?

First, I fired up my trusty old laptop. It’s a bit slow, but it gets the job done. I wanted a place to keep all my notes organized, so I just created a simple text document. Nothing fancy, just somewhere to dump the data.
Then, I started looking for a place I could easily see real-time data, when I find it,I started watching the game . With the game on one screen and my text document on the other, I was ready to roll.
The Process
The game kicked off, and I was glued to the screen. Every time a player scored, I jotted down the player’s name and the points. Same thing for rebounds, assists, steals, and blocks. I had my little system:
- Player Name: Just the last name, to keep it quick.
- Points: How many points they scored.
- Rebounds: Total rebounds.
- Assists: Number of assists.
- Steals: How many steals.
- Blocks How many Blocks.
It was pretty basic, I have to admit. I wasn’t tracking fancy stats like plus/minus or anything. Just the core stuff that even a casual fan like me can easily follow.
Manually tracking everything was a bit of a scramble, especially during fast breaks. There were definitely moments where I thought, “Did I get that right?” But I did my best to keep up. It’s way harder than it looks when you’re trying to be accurate!
By the end of the game, I had a messy but complete record of the key stats for each player. I wasn’t trying to do any deep analysis, just wanted to see the raw numbers for myself.
So, that’s it! That was my low-tech, slightly chaotic, but ultimately satisfying way of tracking player stats for the Kings vs. Pelicans game. It’s not perfect, but hey, it’s my way of getting a little closer to the * I should try a spreadsheet.