From the Command Line to a Chess Engine

It started, like a lot of good rabbit holes do, with simple curiosity. I’d just gotten a new MacBook Pro, and instead of treating it like an appliance, I wanted to understand what it could actually do. That curiosity led me straight to the one app most people never open: the terminal.

At first it was about as basic as it gets. I learned cd to move between folders, ls to see what was inside them, and clear to wipe the screen when things got messy. Small stuff — but there was something satisfying about talking to the machine directly instead of clicking around. The more I poked at it, the more I wanted to know how the command line actually interacts with the system underneath.

Then the project found its purpose. I’m a chess player, so it felt natural to point all this new curiosity at something I already loved. What began as a few commands snowballed into a full-scale chess analysis project. I leaned on AI as a learning partner to help me figure things out as I went — writing my first Python scripts, wiring up the Stockfish chess engine to analyze positions, using Homebrew to install the packages I needed, and learning how Git works so I could track my progress and not lose my work.

What surprised me most was how one small question — “how does this computer actually work?” — kept opening doors to bigger ones. Chasing that thread exposed me to so much more than I expected: Python, Git and version control, virtual environments, working with APIs, building HTML websites, and using Visual Studio Code alongside Claude Code to move faster and learn as I built.

None of it felt like studying. It felt like building something I cared about and picking up the technical skills along the way. This project turned an idle curiosity about my laptop into a genuine technical foundation — and honestly, it’s a big part of why this blog exists. I’m excited to keep building, and I’ll be sharing more about the chess platform as it grows.