Removed old doc, noted how solutions reduce scope

Author: mcasperson

Platform Engineering for Dummies.edited.odt

@@ -34,39 +34,33 @@ <h2>What is DevOps Not?</h2>
 
 <p>There is no satisfying answer to that question. The term DevOps has become almost unfalsifiable, but this is quite by
     design. DevOps has unashamedly sought to break down silos and absorb responsibilities that previously separated
-    teams
-    creating and delivering technical solutions, while simultaneously building a culture of psychological safety to
-    encourage creative problem solving. The ideal DevOps team is self-sufficient, with the ability,
-    willingness, confidence, and responsibility to tackle any and every problem.</p>
+    teams creating and delivering technical solutions, while simultaneously building a culture of psychological safety
+    to encourage creative problem solving. The ideal DevOps team is self-sufficient, with the ability, willingness,
+    confidence, and responsibility to tackle any and every problem.</p>
 
 <p>But for every ideal DevOps team thriving on the responsibility of owning their own destiny, there is another team
-    slowly
-    drowning under the constant need to resolve every brittle process and incorporate every new responsibility
-    encountered in the DevOps lifecycle. The mental
-    burden of this undifferentiated and unsatisfying work has come to define their existence, leading to a downward
-    spiral of dispirited and low performing teams. Or, put more simply, teams with an unsatisfactory developer
-    experience.</p>
+    slowly drowning under the constant need to resolve every brittle process and incorporate every new responsibility
+    encountered in the DevOps lifecycle. The mental burden of this undifferentiated and unsatisfying work has come to
+    define their existence, leading to a downward spiral of dispirited and low performing teams. Or, put more simply,
+    teams with an unsatisfactory developer experience.</p>
 
 <p><i>
     I found myself working as a developer on a codebase whose test suite would fail far more often than it passed. A few
-    manual retries
-    would solve the issue and ensure that pull requests could progress, although retrying the tests could take days.
+    manual retries would solve the issue and ensure that pull requests could progress, although retrying the tests could
+    take days.
 </i></p>
 
 <p><i>
     The suggestion proposed by the engineering leadership at the time was that everyone should stop what they were doing
-    and fix the
-    tests. This is typically sound advice and very much in line with practices like Test Driven Design (TDD).
-    Unfortunately, every developer
-    on the team intrinsically understood that fixing the tests was a dedicated project it its own right. There were no
-    quick wins.
+    and fix the tests. This is typically sound advice and very much in line with practices like Test Driven Design
+    (TDD). Unfortunately, every developer on the team intrinsically understood that fixing the tests was a dedicated
+    project it its own right. There were no quick wins.
 </i></p>
 
 <p><i>
     This forced everyone to quietly calculate the tradeoffs between wasting days on test retries and devoting weeks to
-    undertaking
-    the unplanned work of fixing the tests. Needless to say, we ended up wasting a lot of time clicking that retry
-    button.
+    undertaking the unplanned work of fixing the tests. Needless to say, we ended up wasting a lot of time clicking that
+    retry button.
 </i>
 </p>
 
@@ -130,7 +124,9 @@ <h2>What is Platform Engineering?</h2>
 </ul>
 
 <p>It is easy to see that common solutions to common requirements are the only sustainable path for growing
-    DevOps teams.
+    DevOps teams. While the unfalsifiability of the responsibilities assigned to DevOps teams is still a concern, common
+    solutions to common requirements do reduce the scope of those responsibilities that DevOps teams must
+    actively focus on.
 </p>
 
 <p>In our hypothetical scenario, the obvious solution is to deploy a CI server. But CI servers had to start somewhere.