
Minute one: what is being decided
Read the invitation and the ticket it links to. Write the decision as a question. If you cannot, that is your first contribution to the meeting: ask what the group needs to decide before it ends.
Minutes two to four: the code it touches
- Take two or three names from the agenda: an endpoint, a job, a table.
- Search for each and open the place where it starts.
- Note the file names and when they last changed.
Minute five: one fact and one question
- The fact is something you checked yourself, such as how many attempts the consumer makes today.
- The question is what you want out of the meeting.
A note that fits on a sticky
Decision: where does the retry logic live?
Code: src/queue/consumer.ts (one attempt, no retry)
src/payments/charge.ts
Fact: a failed job stays failed today.
Question: can a retry charge the customer twice?What to skip
- The whole history of the thread. Read the last message and the first.
- Slides you will be shown anyway.
- Understanding everything. You need enough to ask a good question.