# Your first weeks on a new codebase: follow the meetings before you know the code

> In your first weeks the meetings move faster than your reading. Learn the words, learn where things enter the system, and ask questions that show you looked.

Source: https://hintvo.com/blog/first-weeks-on-a-new-codebase | Last updated: November 20, 2026 | Reviewed: 2026-11-20

In your first weeks the meetings move faster than your reading. You will not learn the codebase before the next call, so aim lower: learn the words, learn where things enter the system, and ask questions that show you looked.

## Build a glossary on day one

Every team runs on a few dozen words: service names, table names, acronyms, the nickname of the old billing system. Write each one down with a single line and the place it lives in the code. This list will carry you through more meetings than any architecture diagram.

## Read the edges before the middle

- **Routes and endpoints.** What the outside world can ask the system to do.
- **Jobs and queue consumers.** What the system does on its own.
- **The database schema.** What it remembers.

The middle, where the clever code is, can wait. Most meeting questions are about the edges.

## Five minutes before each meeting

1. Read the agenda or the ticket.
2. Search the code for the two or three names in it, and open where each one starts.
3. Write one question.

## Ask questions that carry evidence

"How do orders work?" asks someone to give a lecture. "I see orders are written in two places, checkout and the admin tool. Is that on purpose?" shows that you looked, and it often finds something real.

## Use the fact that you are new

You are the only person on the team who can still see what is confusing. Write down what the README did not tell you and what the setup script got wrong. Fixing those is a good first contribution, and the next new person will thank you.

## What to stop worrying about

Nobody expects you to know the history. "I have not read that part yet" is a complete sentence. Say it early and often, and replace it with "I read that part yesterday" as the weeks go on.

> **Where Hintvo fits:** type what the next meeting is about and Prepare me writes a one-page briefing from your code: what to know, the words you will hear and good questions to ask. During the call, a term you have not met is explained in one sentence, in the context of your project. Prepare me briefings need a pack of hours. See [the nine scenarios](https://hintvo.com/scenarios).

## Related

- [Hintvo AI in real meetings and interviews: 9 scenarios](https://hintvo.com/scenarios.md): What does Hintvo AI actually do in a real meeting or interview?
- [How to prepare for a technical meeting in five minutes](https://hintvo.com/blog/prepare-for-a-technical-meeting-in-five-minutes.md): How do I prepare for a technical meeting when I only have five minutes?
- [How to explain a technical term in plain words](https://hintvo.com/blog/explain-technical-terms-in-plain-words.md): How do I explain a technical term to people who are not engineers?
