Key Takeaways

• Pull Request-based async code reviews are a prevailing way of reviewing code in our industry
• When feedback is invited only after making a lot of changes, it becomes very difficult for both the PR reviewer(s) and the author to course-correct and build in quality
• Delays are an inherent property of asynchronous reviews, and they increase PR batch transaction cost
• With small Pull Requests, we lose throughput if we review them asynchronously because delays in communication start dominating PR lead time
• Co-creation patterns, Pair and Mob Programming enable continuous code review which enables both high throughput and high quality

idée de format de kata : "Skill issue"

Basée sur l'idée de "mauvaise foi dans le code, bonne foi dans les tests". (poke @romeu )

Driver joue le rôle d'un agent IA de mauvaise foi.

Driver dispose de quelques fichiers  skill.md initialement un peu ambigües.

Driver les interprète de la pire façon.

Ensemble du groupe doit changer ses instructions et/ou les skills pour que Driver fait ce qui est attendu.

Le kata se fait sans L'utilisation de vrai LLM (indeed completion AI)