0.6 How to not get stuck
| Situation | What to do |
|---|---|
| "I don't understand this paragraph" | Read the next two paragraphs. Usually resolved. |
| "I still don't understand after 20 min" | Write the question in notes.md, mark TODO, move on. Return in 2 chapters. |
| "The code doesn't run" | Read the LAST line of the error. Check your .venv is activated. Copy the error into a search engine. |
| "I understand it but can't explain it" | You don't understand it yet. Re-read only the "How it works" section, then try again. |
| "This feels too slow / too basic" | Skip to the Practice section. If you can do it, move to the next chapter. |
| "I'm overwhelmed by all the terms" | Appendix A is a plain-language glossary. Bookmark it. |
| "Should I learn maths first?" | No. Learn it as needed, driven by curiosity from this guide. |
| "Which programming language?" | Python. It is not close. |
A note on honesty
This guide tells you when something is simplified, when it is contested, and when nobody really knows. Look for these markers:
Simplified: the real story is more complex; here's the direction it goes.
Debated: researchers disagree; here are the sides.
Facts, dates, and numbers in this guide were checked against primary sources (papers, model cards, official docs) — see Appendix E for the citations. Model names, prices, and benchmark scores change fast; treat any specific number as "true when written, verify before you rely on it."