docs(day2): Added devex talk

content/_index.md

@@ -17,6 +17,8 @@ After a short talk with my boss, I got sent there by my employer [DATEV eG](http
 I'd say that attending CNS Munich 2025 was worth it. The event is pretty close to my place of employment (2hrs by car or train) and relatively small in size (400 attendees). The talks varied a bit - the first day had a bunch of interesting talks but the second day indulged in ai-related talks (and they were not quite my cup of tea). This might me fine for others but I've heard enogh about ai use cases for the coming years at the last events i attended (or just reddit).
 Maybe disributing the ai-talks over the two days - while always providing an interesting alternative - might be the right move for next time.
 
+Apart from AI many talks focused on Platforms and Platform Engineering
+
 ## And how does this website get it's content
 
 ```mermaid

content/day2/07_devex.md

@@ -0,0 +1,69 @@
+---
+title: Creating a smooth Developer Experience: from complexity to simplicity
+weight: <index of talk on the day>
+tags:
+ - dx
+ - devex
+---
+
+<!-- {{% 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 %}} -->
+
+## Why?
+
+- Complexity in software fev is increasing
+- Kubernetes itself is simple, but the landscape is gigantic
+- Automation reduces complexity, but creating automation adds complexity
+
+## Cognitive Load
+
+- Instrinsic Load: Natural complexity of a task
+- Germane: Effort needed to build expertise and optimise workflows
+- Extraneous: Unnecessary load caused by poor tools or processes combined with distractions
+
+## Example for the rest of the talk
+
+1. Dev: Needs Environment
+2. Ops: Sets up the env in multiple steps
+3. Dev: Receivs new env
+
+### Problems
+
+- Maybe the ops person has no time
+- Doing things via tickets takes a shit ton of time
+
+## Our Lord and savior: Platform Engineering
+
+1. Centralize
+2. Automate: Automate the devops cycle
+3. Simplify: Solve complexities associated with the cloud
+4. Efficency: Avoid bottlenecks
+5. Quality and Reliability
+6. Self-Service
+
+### Circular Economy
+
+1. When a team creates a service, it can it to a marketplace
+2. Another team cann use it, kustomizue it and publish the customized version to the marketplace
+
+## Metrics
+
+- The invisible engine behind every innovation -> No improvement with out proving it
+- Who wants to know what?
+  - User: Wants to measure the platforms impact on dx and productivity (Feedback, Provisioning time, ...)
+  - Org: How does the platform support org efficiency and delivery speed (Time to market, cost savings, ...)
+  - Platform: Stability and team effectiveness (Mean Time to Resolution, uptime, ...)
+- Metric-Frameworks: DORA (DevOps Research and Assesment), SPACE (Satisfaction Performance, Activity, Communication and Efficiency)
+
+## And how do we drag AI into this?
+
+- Frameworks kann make dx measureable
+- Challenge: NEw tools and processes can create friction
+- AI Can help with: Assistance, Code generation, Debugging, Conversational explaination instead of reading docs yourself
+
+## Tips
+
+- Adopt the right mindset (Why a platform, what do i need and how would it impact exsisting metrics)
+- Invest in a effortles selfservice experience
+- Gradualy move habits towards the platform - don't force everything at once
+- Create solutions that people enjoy using