How to Learn a Codebase With No Docs

Wed, 29 Jul 2026 09:00:00 -0500

The hardest case: no tests, no architecture decision records, no diagrams. The tactics shift from consuming documentation to producing it as a byproduct of exploring.

Here’s what that actually looks like, walked through on one example: you’ve just joined a team maintaining Ledger, an internal core-banking service written in Go. Nobody’s written a README beyond make dev. You have a week before you’re expected to ship anything.

Start outside the code

Use the product as a user before you read a line of source. Check the error monitoring dashboards, Sentry, Datadog, early: they show where the system actually breaks, which tells you more than reading happy-path code ever will. The production error log is an honest account of what the system struggles with. The codebase only shows you what the engineers thought would happen.

Onboarding on rjrowland

How to Learn a Codebase With No Docs

Start outside the code