Foundations

Every install guide's first line is 'open a Terminal.' You open it, see a dark window and a line of text, and don't know where to look next. This isn't a command list — it dissects the screen in front of you line by line: what that window is, why typing can make things happen, what the prompt is telling you, and the invisible but always-active 'current directory.'

The first line of most AI-tool install guides is 'open a Terminal,' but nobody explains how Terminal, Shell, and CLI actually differ. This article separates the three terms, gives you ten commands that really are enough, shows you how to read error messages, and covers the habit that costs beginners the most.

The difference between absolute and relative paths, why macOS/Linux and Windows use different separators, what the home-directory shorthand is, why names with spaces need quotes, and how to find where a file actually is on your system. The five most common path errors with their verification methods.

You copy a command from a tutorial, paste it into your terminal, and get a syntax error or command not found — this article explains the four most common reasons: smart quotes, truncated multi-line commands, invisible whitespace characters, and pasting into the wrong shell. Each comes with an immediate verification method.

An API is a published agreement; an SDK is a toolkit in which someone has wrapped the details of calling that API for you. This piece spells out the difference between the two, why some tools require an API key and some do not, the distinction between REST and streaming, and whether you, as a user, ever need to write API calls yourself.

Why API docs are full of status codes and headers. This article walks through a real request to clarify the four parts of HTTP — request, response, status code, header — then explains the difference between WebSocket and polling, why CORS blocks you, what a proxy does in the middle, and why SSH and private keys belong to the same family.

An API key is a string that tells a remote service 'this request is yours, and the bill goes to you.' This article explains why it's a secret, where it belongs (environment variables or .env — never a chat window), what to do on leakage, why it's usually wired directly to money, and a distinction most beginners miss: logging into the web version is not the same as having an API key.

Error messages aren't meant to be read word by word — they have a fixed shape: a concluding line, a stack trace, a filename with a line number, and an exit code. This article teaches why you read a stack trace bottom-up, how to find the line that actually failed, six real-shaped examples, and when to paste the whole thing into a search engine, when to give it to an AI Agent, and when to do neither.

Why every AI programming tool's installation guide assumes you know Git. This article explains what repository, commit, branch, clone, fork, and pull request each mean, how they connect, and why non-programmers need to understand the first three.

Why every tool asks you to edit a file starting with a dot, the difference between YAML and JSON, why wrong indentation breaks everything, what problems package managers like brew and apt solve, and how much regex you actually need to know.

Build a development environment that can call an LLM API from scratch: installing Python, virtual environments, getting an API key, and managing environment variables, then verifying the whole chain with a single curl command. Complete commands for both macOS and Windows, with a focus on keeping your key safe and out of git.

When a tool seems unresponsive after installation, it's almost always one of five reasons: not in PATH, insufficient permissions, network blocked, version mismatch, or low disk space. This guide provides a one-minute check for each reason and explains why 'reinstalling' is rarely the solution.