the two loops
Two iteration loops in onboarding to someone else's project.
Tech: read code, find what's broken, propose fixes. Comms: read tone, draft, calibrate, send.
Most writing about AI-paired work covers exactly one. Pair-programming articles cover the tech loop. Founder-DM-coaching content covers the comms loop. They sit in different stacks.
Tonight: the loops compound. They don't sit side-by-side. They feed each other.
concrete
Audit found 3 failing tests on telegram main. Not flaky. Real. Caused by commit 7107c49 that introduced a native-fetch path the tests never updated to mock. Diagnosed it in five minutes. That diagnosis turned into one line in the WhatsApp message: "Small PR tomorrow." Without the diagnosis, the message would have ended on a teaser. With it, the message ended on proof-of-work-in-flight.
Other direction: the comms iteration produced calibration. "Nothing urgent / your tone / sacred stays as-is / small PR tomorrow." That calibration informed how the PR body would be written. Universal voice in the PR. French-flavored direct in the WhatsApp. Two registers, one work surface, one comms surface. The comms work taught me the voice-rule for the PR. The PR work gave me proof-of-work for the message.
the iteration
Drafts on the WhatsApp message: 5 questions → 2 → 1 + bug heads-up + warm sign-off. Each pass dropped soft verbiage. The drops were possible because the parallel tech iteration was producing facts that replaced softness. "I read the code seriously" → "Discord on 2026.403.0 vs others on 2026.318.0." "I'll be a good co-maintainer" → "Sacred stays as-is, small PR tomorrow."
the unit changed
Stopped being "ship the PR." Stopped being "send the message." Became "ship the integrated artifact: message that references the PR that reflects the audit that respects the maintainer's tone." Compounding only happens when one mind sees both axes.
insist on this
AI doesn't help on track A while you help yourself on track B. AI work on each track lowers the cost of work on the other track. The relationship has gear teeth.
If comms had been blocked (the maintainer's voice unclear, my register off), the PR ships without integration. Just code. Less leverage.
If tech had been blocked (no real bug to find), the comms is more abstract. Fewer things to cite. Less proof.
the principle
Compound, not sequential. The loops feed each other. AI changes the unit, not just the speed.
Track this.
The next time someone asks "did AI make you faster?" — wrong question. The right question is "did AI change what the work is?"