Troubleshooting
Fix it in order¶
When something breaks, people reinstall everything, try random fixes, and make it worse. This order works for almost any computer problem — AI-related or not.
The universal order¶
- Read the actual error. Copy the exact message. Don't summarize it as "it's broken" — the message usually names the problem.
- Change nothing; try again once. Lots of failures are one-time hiccups.
- Ask: what changed? It worked before. What's different — an update, a new file, a rename, a different folder?
- Shrink the problem. Does it fail with a tiny test file? In a fresh folder? Finding where it works tells you where it breaks.
- Search the exact message. Paste the error, in quotes, into a search engine or an AI.
- Then, and only then, reinstall.
Ask AI the right way¶
Copy this
Something failed. Here's the exact error message: [paste it].
Here's what I was doing: [one sentence]. Here's what changed
recently: [anything you know]. Walk me through fixing it one
step at a time — one step per message, and tell me what each
step does before I run it.
The "one step per message" part matters — it stops the AI from dumping ten commands you can't judge.
By system¶
- Terminal basics — the five commands that cover 90% of it.
- Windows · macOS — the usual suspects on each.
- Git & Codespaces — for site and code projects.