Calendar:Development Strategies: Difference between revisions

Because everyone is better sync throughout, much of the feedback being requested requires less time on the part of the code owner than dealing with one big patch of the end of the process.  In other words, even though there are more points at which blocking can happen, the total amount of time actually spent in a blocked state is often less.

Note that these are just guidelines that are subject to judgement calls, not hard and fast rules.  Five-line patches generally don't need this level of coordination.  Sometimes it makes sense to discuss UI design and code-level strategy together.  A quick prototype may occasionally be useful.  Implementation will sometimes turn up issues that effect the design.  Furthermore, these guidelines are not a magic bullet: occasionally patches end up needing to be re-written for one reason or another, despite everyone's best efforts.  But in general, they're pretty good at avoiding unnecessary work.