Reading a monolith without boiling the ocean
A practical order of attack for consultants and internal leads facing a multi-decade line-of-business application.
You will not understand every class. Pretending otherwise burns budget and patience. The goal of early reading is to locate load-bearing routes: authentication, money movement, inventory posts, and the batch edges that fire when nobody is watching.
Enter through operations, not frameworks
Ask which screen staff open first on a busy morning. Trace that click to the data store. Framework upgrades matter later; the morning path matters now.
Sketch interfaces on paper
Boxes and arrows that name queues, files, and COM calls beat a generated UML dump nobody trusts. Hang the sketch where sponsors can correct it.
Time-box curiosity
Set a reading budget per module. When the timer ends, write what you know and what remains opaque. Opacity is a risk entry, not a personal failure.
AmberPath uses this discipline inside every technical debt audit and flagship modernization. Curiosity is a tool; open-ended wandering is not a deliverable.