wiki.accu.org

User Tools

Site Tools

Trace: • java_is_dead_long_live_scala_kotlin_ceylon_etc • functional_c • the_c_memory_model_for_concurrency • programming_to_d_max • scrum_patterns • spreadsheets_for_developers
2015:archipelagos_in_git

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
2015:archipelagos_in_git [2015/04/01 10:09] – jonjagger2015:archipelagos_in_git [2016/06/11 14:05] (current) – external edit 127.0.0.1
Line 6: Line 6:
 **Duration**: 15 mins\\ **Duration**: 15 mins\\
 **Description**: \\ **Description**: \\
-Island: Any piece of sub­continental land that is surrounded by water.\\+Island: Any piece of subcontinental land that is surrounded by water.\\
 Archipelago: Island chain, is a chain, cluster or collection of islands.\\ Archipelago: Island chain, is a chain, cluster or collection of islands.\\
 \\ \\
 Assumptions:\\ Assumptions:\\
-  * ­Reviewing code is a worthwhile activity +  * Reviewing code is a worthwhile activity 
-  * No one wants to review and/or merge code as their full­time job+  * No one wants to review and/or merge code as their fulltime job
   * No one person should bear all that responsibility anyway   * No one person should bear all that responsibility anyway
-  * ­Existing, non­conceptual approaches to the problem of managing the movement of code are quite weak +  * Existing, nonconceptual approaches to the problem of managing the movement of code are quite weak 
-  * Communication is always required and goes a long way to solving many of our problems, but we can't all communicate with everyone all the time on a medium­ large team+  * Communication is always required and goes a long way to solving many of our problems, but we can't all communicate with everyone all the time on a medium large team
   * Metaphors help understand intent   * Metaphors help understand intent
   * Sometimes code will need to be shared between teams; it isn't always possible to divide up work by features (although appropriate interfaces help with this)   * Sometimes code will need to be shared between teams; it isn't always possible to divide up work by features (although appropriate interfaces help with this)
Line 31: Line 31:
   * Archipelagos can be near or far away from each other ­ sometimes they will want to merge between each other, but this is not particularly desirable unless you combine   * Archipelagos can be near or far away from each other ­ sometimes they will want to merge between each other, but this is not particularly desirable unless you combine
   * How do we know when to create an archipelago?   * How do we know when to create an archipelago?
-  * Feature files / executable specification.... where does it fit in?+  * Feature files / executable specification, where does it fit in?
   * Realisations from actual use with several teams totalling 20+ developers\\   * Realisations from actual use with several teams totalling 20+ developers\\
 \\ \\
 \\ \\
  
2015/archipelagos_in_git.1427882991.txt.gz · Last modified: 2016/06/11 14:05 (external edit)