Learning pathsA
The working loop

Orient in an unfamiliar codebase

Find the execution path before asking for edits.

Understand the problem

Read the entrypoint, data contracts, adjacent tests, and one representative request path. Identify the smallest place a change belongs. Record assumptions about state and side effects.

Make it concrete

For a failing checkout, trace controller → service → gateway adapter before rewriting the controller.

Trade-offs and pitfalls

Broad context collection consumes time; focus on the requested behavior.

Check your understanding

Map one feature from user input to persistent state.

Practice this topic

Your study notes