# 1:1 guide: dev-3 App squad. Last 30 days, compared with the 30 days before. Context I gave: they led the AI Activities reports, no vacation, no on-call. Source: DevStats MCP. **The short version:** this person had the biggest month on the squad and also reviewed more than before. Almost everything that looks slow in their numbers is time their work spent waiting for us. Go in to say thank you and to find out what it cost them. ## 1. Recognize **Four reports shipped in one month.** Claude Console (#7247), Claude Enterprise (#7294), Cursor (#7362) and Devin (the stack from #7406 to #7432, closed out in #7501). They came with new data schemas, sync backends and connect flows. 149 PRs merged against 124 the month before, 125 issues resolved against 84. Name the reports, not the counts. **They did not stop reviewing to do it.** 108 reviews given, up from 76, and the reviews got deeper: 0.44 comments per review, up from 0.13. Most people who carry a project this size go quiet in other people's PRs. They did the opposite. One more, if there is time: the Devin work was sliced well. 14 PRs between 92 and 1,406 lines, each tied to one issue, with the feature flag (#7424) as its own PR. That is how a large project should look in review. ## 2. Ask about **"I noticed the Devin PRs sat for days before anyone picked them up. What was that like from your side?"** 9 of their 15 slowest PRs waited between 3d 16h and 4d 14h for a first review. 13 of the 15 have zero coding time, so the work was done when the PR opened. They were finished and waiting on us. **"You seem to have a lot more open at once than a month ago. Is that the project, or are you being pulled into other things?"** Daily WIP shows 111 open tasks in the period against 29 the month before, and 3 open branches against 2. The task count is a rough signal, so treat it as a direction and let them tell you what is behind it. **"A good part of your activity happens in the evening. Is that the schedule you want, or is the day getting eaten?"** 36% of their activity is after 6pm and 23% is after 8pm, Monday to Thursday. It was the same the month before (38% and 26%), so this is a habit and not a crunch. Two things soften it: there is no weekend activity in either month, and only 4% happens before 10am, so they may simply work a later day. Ask as care. Do not praise the hours, and do not assume a problem. ## 3. What I owe them **Faster first reviews.** Pickup time on their PRs went from 11h 35m to 14h 55m while they were shipping the most on the squad. Their own review time is short (1h 55m). The wait is ours. Concrete offer: a named reviewer for their next stack, and the stack reviewed in one sitting. **A release path that does not hold their work.** Their PRs wait 1d 20h between merge and production (1d 22h the month before). That is most of their 2d 20h cycle time, and none of it is in their hands. The Devin report had its flag and still shipped as one launch. **Cleanup PRs should not queue behind features.** The two integration removals (#7250, 1,462 lines, and #7249, 3,441 lines) waited 2d 21h and 2d 17h for pickup. Deletions are the easiest reviews there are. I should have caught those. ## 4. Growth topic **Landing a big project, not building it.** They already slice well. What is left is the last step: three PRs this month were above 10,000 lines (16,873, 10,692 and 10,401), and the Devin close-out (#7501, 10,692 lines) went in with 1 review and no measurable review time. Nobody can review that, and it is where the risk of a project concentrates. The conversation: how would they ship the next report so that there is no close-out PR at all, with each slice going to production behind the flag as it merges? They have now done this four times. They are the right person to write down how the squad should do it. ## 5. Leave out - **Their PR cycle time is the longest on the squad** (2d 20h, in a squad range of 1d 11h to 2d 20h). It is pickup and deploy wait, covered above as things we owe them. Do not present it as their number. - **Average PR size of 410 lines, up from 332.** Three PRs above 10,000 lines pull the average. The typical PR in the Devin stack is a few hundred lines. - **Issue cycle time moved from 22h 37m to 1d 1h 57m.** Too small to mean anything. - **Issue types.** 99 of their 125 issues (79%) are typed "Other", so the feature and bug split cannot be read. What is labeled is 24 features, 1 enhancement, 1 bug and 0 hotfixes. There is no sign of a month spent on firefighting. - **Activity roughly doubled** (2,268 events against 1,092). It follows the project. Counting events says nothing about the person. --- *Waiting times per PR are converted from the seconds returned by PR List. Evening shares are the 6pm to midnight and 8pm to midnight windows of the Activity Heatmap divided by all events in the period. The squad range covers the four people with merged PRs in both periods.*