One project, three binaries
When you install FFmpeg, you actually get three command-line programs. Most people only know about the first one, but all three matter:
ffmpeg— the workhorse. It transcodes, transmuxes, filters, streams. Almost every chapter of this quest is aboutffmpeg.ffprobe— the inspector. It reads a file and tells you what's inside: container, streams, codecs, bit-rates, color space, duration, frame count. It never modifies anything. This is your X-ray.ffplay— a tiny SDL-based player. It's not a competitor to VLC; it's a debugging aid for filtergraphs and weird streams. Most days you won't use it. The days you do, you'll be glad it exists.
Some Homebrew/Linux builds compile ffplay out by default (it depends on SDL2). On macOS via Homebrew it's there. If which ffplay returns nothing on your system, you have ffmpeg and ffprobe only — that's fine, you can preview with open, vlc, or QuickTime instead.
Probe-first, then encode
The single most important habit to build is probe before you encode. The reason a thousand FFmpeg jobs go sideways is that someone guessed at the input — assumed it was 30 fps when it was 29.97, assumed audio was stereo when one channel was muted, assumed the resolution from the filename. Two seconds with ffprobe kills that whole class of bugs.