docs(day0): Added extensible platform talk

content/day0/12_extensible.md

@@ -0,0 +1,45 @@
+---
+title: Building Extensible Platforms
+weight: 12
+tags:
+ - <tag>
+---
+
+<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
+<!-- {{% button href="https://docs.google.com/presentation/d/1nEK0CVC_yQgIDqwsdh-PRihB6dc9RyT-" style="tip" icon="person-chalkboard" %}}Slides{{% /button %}} -->
+{{% button href="https://colocatedeventseu2026.sched.com/event/2DY7J" style="error" icon="calendar" %}}Sched Link{{% /button %}}
+<!-- {{% button href="https://github.com/graz-dev/automatic-reosurce-optimization-loop" style="info" icon="code" %}}Code/Demo{{% /button %}}  -->
+{{% button href="https://hazelweakly.me/" style="info" icon="link" %}}Website/Homepage{{% /button %}} 
+
+
+## Baseline
+
+Complexityis unavoidable: May it be in platforms, physics or biology
+Complexity usually grows rappidly followed by a phase of making things better -> "Let's make virtual machines easier but add 500x more of them" (the story of kubernetes)
+
+TODO: Steal chart from slides
+
+## Mthods to the madness
+
+- We want confluence (the mathematical one, not the atlassian one): If there are different paths that are semanticly the same it should not matter wich path we take
+  - As long as we achive the same goal the specifics should not matter that much
+- Narrow Protocol: A narrow and slowly evolving protocol allows us to have diversification below and above the narrow point
+  - Examples: IP Adresses and DNS haven't changed in a long time -> We can use this narrow thing to build monsters on top of
+  - Allow everything above and below your platform to change flexibly and evolve
+- Vertical integration: When you're getting integrated you become valuable (again the DNS example) -> Vertical integration always beats technological capabilities
+- Picking the right protocol might be hard, but choosing a narrow and integrated one helps
+
+TODO: Steal confluence slide
+
+## Extensibility
+
+- The expression Problem: The static typesafety vs type-flexibility question 
+- So we want a platform where we can
+  - In a typesafe manner
+  - onboard new applications into the platform
+  - onboard new integrations into the platform
+  - Without requiring a end-user or platform migration/deploy
+  - Without centralising definition of interfaces or applications
+  - Without assuming a certain platform or applicationg architecture
+- So basicly: Protocolas are the new platforms
+- You have to be fine with people using your protocol for whatever they want -> It needs to be abusable