Reading Unfamiliar Code

Programming FoundationsLesson 8 of 875 minutesLab included

Learning objectives

By the end of this lesson

• Inventory entry points, inputs, outputs, and important state.
• Sketch function and control-flow relationships.
• Separate observations, hypotheses, and conclusions.
• Design boundary tests before making source changes.

Do not begin at line one and hope

For a small unfamiliar program, first locate:

1. The entry point: top-level Python code or C main.
2. External input: arguments, files, or standard input.
3. Output and effects: printed text, written files, and exit codes.
4. Functions called from the entry point.
5. Conditions and loops that decide what happens.
6. State that changes along those paths.

Then draw a small map. Names such as parse, validate, and save are hints written by the author, not proof of behavior.

Trace one value

Choose one externally controlled value and record each transformation:

Step	Location	Value/type	Evidence
Entry	argument or file	text	input interface
Conversion	parser	integer or structured value	conversion call
Decision	condition	compared value	branch expression
Effect	output	result	print/write/return

Mark assumptions: required length, permitted range, terminator, successful allocation, or expected file format. Each assumption suggests a boundary test.

Test before editing

Run a normal case, empty case, exact boundaries, just outside each boundary, wrong type, and unexpectedly long input. Record predictions first. If behavior contradicts the map, revise the map before modifying code.

Temporary print statements can confirm state, but keep a clean copy and change one observation point at a time. Instrumentation can alter timing and state; it is evidence with limitations, not divine revelation.

Knowledge check

Question 1 of 2

What should an unfamiliar-code map begin with?

Entry points, external inputs, effects, and major callsEvery punctuation mark in orderA guess at the final vulnerability

Check answer

What this gives us as researchers

You now have a repeatable source-level investigation process. The Code Investigation Lab asks you to apply it without being handed the command sequence.