Studying Code, Docs and Technical Material
Documentation, a framework you have to pick up by Monday, a language you are learning properly rather than by copying snippets — all of it works the same way as any other topic. This page covers how to get technical material in, what the explanations include, and the one place audio is the wrong tool.
It Works the Same Way, With Code in the Explanations
A technical topic behaves like any other: it becomes a roadmap of subtopics, Explain Mode walks you through them, and the explanations include worked code examples alongside the diagrams and callouts. Then Quiz Mode and Exam Mode question you on it. The useful difference from reading documentation is that documentation never asks you anything back.
Getting Technical Material In
- Documentation as a PDF — most docs sites and API references can be printed or exported to PDF, and that uploads normally.
- A technical book or course PDF — upload it in chapters rather than whole, so each topic stays a workable size.
- Or just describe it — "the React hooks lifecycle", "how transformer attention works", "OAuth device flow". For a well-established technology this is often faster than finding a document, and it is the route your free credits cover.
- Not a repository — you cannot point it at a GitHub repo or a URL, and it does not read a codebase. Upload the docs or describe the concept instead.
Audio Is the Wrong Tool for Code
Read It Aloud speaks text as it is written, which means a code block is read out symbol by symbol and becomes unusable noise. This is a real limitation and worth knowing before you try it on a technical section. The spoken conversation handles it differently and better: it is instructed never to read code, a URL or a table aloud, and to say instead that it is on screen and describe what it does.
Explaining a Technical Idea Out Loud
This is where technical material rewards the spoken conversation most, because so much of a developer's job is explaining a decision to someone else. Talk through why you would use a queue here, defend a schema choice, or try to explain what you think a piece of code does — and get pushed on the parts you were hand-waving. It is also the closest rehearsal there is for a technical interview, which has its own page.