# How to answer questions about code you did not write

> A meeting question lands on code someone else wrote. How to answer honestly in the moment: find the entry point, say what you can stand behind, name what you still have to check.

Source: https://hintvo.com/blog/answer-questions-about-code-you-did-not-write | Last updated: November 20, 2026 | Reviewed: 2026-11-20

Most questions that stall a technical meeting are about code the person being asked never wrote. You do not need the whole codebase in your head. You need a way to find the right place fast, say what you can stand behind, and name what you still have to check.

## Separate three kinds of answer

- **What the code does today.** A fact. You can look it up.
- **Why it was built that way.** History. It lives in commit messages, pull requests and the memory of whoever wrote it.
- **What it would take to change.** An estimate. It depends on the first two.

Most bad answers mix these. "It makes one attempt and marks the job failed" is a fact. "It should be easy to change" is a guess in the same tone of voice. Say which one you are giving.

## Find the entry point, not the whole picture

1. Start from the word people used in the meeting: an endpoint path, a job name, a table, an error message. Search for it exactly.
2. Open the place where it enters the system: the route, the handler, the queue consumer.
3. Follow one call down until you reach the line that does the thing being asked about.
4. Stop there. You need one path, not the map.

## Say it in a form others can check

- Instead of "I think it retries", say "The consumer in queue/consumer.ts makes one attempt and marks the job failed. I see no retry there."
- Instead of "That should be fine", say "I checked the charge function. I have not checked refunds."
- Name the file. It lets the room verify you, and it is the fastest way to earn trust on code you did not write.

## When you cannot find it in the moment

Say what you will check and when. "I can confirm that ten minutes after this call" is a good answer. A guess is fine too, as long as you call it a guess. What costs you later is a guess that sounded like a fact.

## Make the next time easier

- Keep a short note per area: where it starts, which tables it touches, who knows it.
- Read the tests. They show what the author meant the code to do.
- Ask the author once, then write the answer where the next person will find it.

> **Where Hintvo fits:** Hintvo reads the project on your computer and listens to the call. When a question about the code comes up, a card shows what to say with the file and line it came from, and a reference that is not in your project is flagged instead of shown as fact. One click opens the line in VS Code, Cursor or Zed. See [how it works in developer meetings](https://hintvo.com/meeting-assistant-for-developers).

## Related

- [AI meeting assistant for developers, with answers from your code](https://hintvo.com/meeting-assistant-for-developers.md): How does Hintvo AI help in sprint planning, design reviews and incident calls?
- [Why an AI answer about your code should name its file and line](https://hintvo.com/blog/why-ai-answers-need-file-and-line.md): How can I trust an AI answer about my own codebase?
- [Your first weeks on a new codebase: follow the meetings before you know the code](https://hintvo.com/blog/first-weeks-on-a-new-codebase.md): How do I keep up in meetings during my first weeks on a new team?
