# Engineering digest: weeks 5–6 A sample two-week engineering digest in the exact format the founder who ran the vetting session sends your team. Source: https://www.wepair.works/artifacts/digest Published: 2026-09-13 Updated: 2026-09-13 Period — Weeks 5–6 Engineer — Senior backend engineer · payments Reviewed by — Bruno Tello Basis — 34 merged PRs, 2 design docs, 1 incident Sent to — VP Engineering, direct, one page An illustrative sample, not a real client engagement. It shows the digest you receive weekly or every two weeks, depending on what your team needs, for the whole engagement at no extra cost. It is written by the founder who ran the original vetting session, after reading the actual diffs. ## The one-line version On track. The reconciliation work is the best thing he has shipped for you. One process problem on your side is costing him review cycles, and it is cheap to fix. ## Signals Work quality — Holding — Shipped the ledger reconciliation job. Read the diff end to end. It is the work of someone who has done this before. The backfill is idempotent and he wrote the rollback before the migration. Throughput — Expected — 34 merged PRs across two weeks, median 180 lines. Down from 41 in weeks 3–4, which tracks the shift from small fixes to the reconciliation work. Not a concern. Friction — Watch — Two PRs came back with review comments about your internal event naming convention, twice for the same reason. It is not written down anywhere he can read. Worth twenty minutes of someone's time. Ownership — Strong — Took the 03:40 UTC page on his own initiative, wrote the incident note, and asked for the on-call rota to be made explicit rather than volunteering again. Correct instinct on both counts. ## What I would do over the next two weeks Write down the event naming convention, even badly, even in a comment at the top of the schema file. He has now guessed wrong twice and both guesses were reasonable. Give him a decision on the on-call rota. He asked for one two weeks ago and has not been told either way, so he is defaulting to picking up pages nobody assigned him. That works until it does not. ## What I raised with him His PR descriptions assume the reader already knows why the change is needed. Fine for your senior reviewers, not fine for the two people who joined last month. He has agreed to lead with the problem statement. He is on holiday for four days in week 8. Local public holiday, notified three weeks ahead, and it is in the invoice adjustment already. ## Where I would push back on you He has been in the payments codebase for six weeks and has not been added to the design review rota. You are paying for the systems reasoning that got him through our gate and currently not using it. This is the second digest in which I have raised it. [See how we place Latin American engineers inside US teams](/hire/latam-developers).