Working on abstractions chapter

Author: mcasperson

_includes/abstractions.html

@@ -83,5 +83,15 @@ <h1><a id="abstractions">The "abstractions with infinite flexibility" fallacy</a
 </ul>
 
 <p>
+    An anti-pattern to avoid when starting a new platform team is focusing to heavily on the centralized responsibility model. This
+    model requires that you build the most accurate abstractions, and starting a new platform team is the time when you
+    have the least amount of information.
+</p>
 
+<p>
+    The shared responsibility model requires platform teams to build workflows that facilitate shared development of
+    artifacts. While tools like Git provide a great foundation for these workflows, platform teams must still invest
+    time in ensuring artifacts can be tracked and merged over time. The benefit of this model is that it provides a
+    direct feedback loop between the platform team and your customers and accepts that the abstractions underpinning
+    your IDPs artifacts will need to evolve over time.
 </p>