From 1a993b4e889021530b5cbba971ac477ab7cb625a Mon Sep 17 00:00:00 2001 From: "Gordon Beeming [SSW]" Date: Mon, 6 Nov 2023 11:33:46 +1000 Subject: [PATCH] Adding quote by Daniel M for co-creation patterns (#7178) --- rules/do-you-use-co-creation-patterns/rule.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/rules/do-you-use-co-creation-patterns/rule.md b/rules/do-you-use-co-creation-patterns/rule.md index 9a2d8ffa37b..73d6ecabacf 100644 --- a/rules/do-you-use-co-creation-patterns/rule.md +++ b/rules/do-you-use-co-creation-patterns/rule.md @@ -53,10 +53,11 @@ That leads us to synchronous, continuous code reviews and co-creation patterns So, with the async way of working, we’re forced to make a trade-off between losing quality (big PRs) and losing throughput (small PRs). -We can avoid this by using co-creation patterns. +We can avoid this by using co-creation patterns. As a general rule, Pull Requests with less than 20 lines of code, and larger changes with a degree of complexity/risk, make good candidates for co-creation -> As a general rule, Pull Requests with less than 20 lines of code, -> and larger changes with a degree of complexity/risk, make good candidates for co-creation +> The idea is that you do small PR's but also limit WIP. If you are do several small PR's quickly and are waiting for review, you become blocked very quickly. By co-creating, the small PR's get reviewed & merged instantly which avoids getting blocked and enables you to smash out loads of small PRs! 💪 +> +> Daniel Mackay ### Patterns