Section 4.2 Studying and working with LLMs

Read a source with an assistant

Course notes, technical documentation and generated prose carry different authority. To study Python behavior, official documentation defines the interface and a test checks what happens in a particular version. An assistant can locate a passage or suggest a case. Keep the primary reference available.

Check claims at the right granularity

The documentation for list.sort describes sorting a list in place. The sorted documentation describes building a new list from an iterable. Claiming that sorted recursively duplicates the contained objects goes beyond that guarantee. To check the third claim, track the identity of a shared mutable element after sorting.

Three rows connect a claim to a source passage and a test. Deep copying is marked as a claim to examine.
Figure 4.2. Evaluating each claim separately prevents an accurate citation from carrying an unsupported extension.

Establish a reading protocol

For each claim, ask for a passage ID, the short quotation that supports it and any required assumptions. When the material is insufficient, preserve an “undetermined” output. In programming documentation, keep the version or commit. In institutional documents, retain the date, scope and page. A citation to the right document can still point to an outdated policy or the wrong group.

Analysis exercise. Identify the missing qualification in “Stable sorting preserves the order of all input elements.” Stability applies to items that share the same key. A sort can move entire groups when their keys differ.