Loading…
Lesson 8 of 11
The AI assistant speeds up learning when used as a coach, not a replacement for thinking. You will learn how to phrase a good question, a debugging ladder, and etiquette that protects your own skills.
What the picture shows: Four rungs in order: read the error, try yourself, ask the assistant with the context, then check its answer by running it.
The concepts in order, click any one to jump to it:
An AI assistant is like a coach at the gym: it explains the move and corrects your form, but it does not lift the weights for you. If it lifts for you, your muscles never grow. Ask clearly, ask it to explain rather than solve, and try its answer yourself before you trust it.
Language models predict the most likely text, so they can be confidently wrong. A good question states the context, goal, constraints and answer format, and includes the full error message. The debugging ladder: read the error, search, ask for a hint, then a solution with its explanation. Always verify by running and testing the code.
So you understand what the assistant suggests and do not run it blindly.
The error message is your first clue and the best thing to give the assistant.
The goal is for you to understand. Ask for the idea, a hint and a direction, then write the solution yourself. Taking a ready answer without understanding can cost you the very skill you came to build.
Four elements: the problem (what you are trying to do), the signal (the error or behavior exactly as it appeared), a tiny guess (what you tried or suspect), then a specific ask (a hint? an explanation? a review?).
Before asking: re-read the error, shrink the problem to the smallest example, test one hypothesis, check the manual, then ask. When you ask, you bring everything you tried.
The assistant can be wrong and sound confident. Run suggestions in a safe place, understand each command before executing, especially delete and permission commands, and compare with the official manual.
Figure 1, The debugging ladder: asking is the last rung, not the first.
| Weak phrasing | Strong phrasing |
|---|---|
| "The command did not work, help" | "I am trying to move a file to the parent directory. I typed mv report.txt .. and got: No such file or directory. I suspect I am not in the right folder. How can I check where I am? Please give a hint, not the full solution." |
| "Write the whole code for me" | "I understand a loop repeats until a condition is met, but I cannot see why mine never ends. Here is what I tried and the result. What should I inspect?" |
| Situation | The right approach |
|---|---|
| You do not grasp a concept | Ask for an analogy and a small example, then explain it back in your own words and ask for corrections. |
| Your code errors | Send the error + the smallest snippet that reproduces it. |
| A strange command the assistant suggested | Ask: what does each part do? What is the worst that could happen? Check man. |
| The myth | The reality |
|---|---|
| The faster I copy an answer, the more I learn. | Learning happens when you try, fail and understand. Copying gives you a result, not a skill. |
| The assistant is always right. | It can be wrong or suggest a command unsuitable for your environment. Always verify. |
| A longer question is better. | A short, specific question with the precise detail beats a flood of text. |
Explaining concepts in several ways until one fits you.
Decoding cryptic error messages and finding a direction.
Explain what you understood and ask for critique.
Make the assistant part of the discussion, not a substitute for it.
Which question is strongest to ask the assistant?
It has the problem, the signal (the error verbatim), a small guess and a specific request: the four parts of the question formula.
Where does “asking” sit on the debugging ladder?
The earlier steps teach you on your own and make your question sharper and the answer more useful.
The assistant suggests a command that deletes a directory. What do you do?
The assistant can be confidently wrong. Delete and permission commands especially must be understood and tried somewhere safe first.
State what it should do, the exact error message, what you tried, and what kind of help you want.
Because the earlier steps teach you directly and make your question sharper and the answer more useful.
Delete, permission-changing, and elevated-privilege commands; understand them and try in a scratch folder first.
Sorted by kind: start with the official docs when you want the precise reference, or with an article or video when you want the explanation first.
Grouped by type. Start with the official docs for precision, or an article or video for the explanation.
Sign in to save your progress.