content/day0/04_sponsored-gitpod.md

@@ -1,26 +0,0 @@
----
-title: "The platform Engineer gauntlent: Three defining challenges in the AI era"
-weight: 4
-tags:
- - platform
- - cloudnativecon
- - sponsored
----
-
-<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
-
-## Conviciton
-
-- Background: There is an absence of platform leadership
-- Reason: Most "leaders" don't push services or features to developers with conviction
-- Solution: Be proud and use your leadership role with courage
-
-## Focus
-
-- Focus on developers
-- Don't only focus on the production ecosystem (observability, ci/cd) but also the path to this end
-
-## Foundations
-
-- Problem: Many companies are running behind their ai goals thanks to missing baseline automation
-- Solution: Embrace the AI

content/day0/04_sponsored-vultr.md

@@ -1,14 +1,10 @@
 ---
 title: "Containerization beyond CPUs - A Kubernetes based serverless platform for ai native applications"
-weight: 5
+weight: <index of talk on the day>
 tags:
- - platform
+ - <tag>
- - cloudnativecon
- - sponsored
 ---
 
 <!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
 
-
+TODO:
-
-Hypothesis: We are at the beginning of a 10 year cycle that is moving towards ai-native applications.

content/day0/06_hire-engineers.md

@@ -1,60 +0,0 @@
----
-title: So you want to hire for platform engineering
-weight: 6
-tags:
- - platform
- - cloudnativecon
----
-
-<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
-
-Hypothesis: The bar for good interviewing is somewhere near the earth's core and we need to improve this (because we need more engineers)
-
-## Resilience engineering
-
-> The overarching concepts that apply to platforms or just "how to make code work"
-
-Idea: Four main goals that align with different roles unter the mothership "resilience engineering"
-
-- Rebound: SRE
-- Robustness: Infra
-- Graceful extensibility: Platform Engineering
-- Sustained adaptability: DevEx (often pulled out into something else)
-
-Bonus things to look out for
-
-- Intellectual Humility: The ability to learn new things and accepting that you might now much but not everything
-- Ecological awe: The awe expereienced when looking at beautiful nature and feeling small or just looking at the cncf landscape
-
-## What do you need for the first team
-
-- People who are able to hire new people and willing to step up to leadership in the long term
-- Generalists
-
-## The process and what to do
-
-What should happen before we hire someone (either in one or multiple interviews).
-
-1. Learn about each other
-2. Solve a technical problem together
-3. Solve a socological problem together
-4. How do you and your future coworkers/stakeholders get along
-
-Make sure the end2end time (first interview to ye or no) is low (best is under two meeks)
-All of your current engineers should be able to pass the interview without studying in advance (no stupid)
-
-## Potential Failures and fallacies
-
-- The fallacy of demographics in = demographics out
-- Treating interviews like hazing
-- you don't track afer-hire indicators
-- Whireboard interviews: They are stupid repetition and regurgitation and have 0 relations to the real world work
-- There are no real studies on how to asses and hire talent
-
-### Flags
-
-- Passion is usually interpreted as "puts up with abuse" and should not be mistaken for caring -> See "Ecological awe"
-- Side projects probably indicate lack in family/social time "i make my wife raise the kids" -> Sideprojects are not a good indicator, maybe their are brilliant at their job but love their free time
-- A Moneyball-like process (data-driven decision) completely counters how talent is perceived -> Expand the hiring pool to anybody and ignore the clasical "indicators of talent"
-- Discriminated demographics probably have a better grip on systems thinking (doe to being forced to make choices)
-- Systems thinking is more important than platform knowledge (If you can think in terms of organization and dependencies you can work on platforms)

content/day0/07_past-present-future.md

@@ -1,60 +0,0 @@
----
-title: The past, the present and the future of platform engineering
-weight: 7
-tags:
- - platform
- - cloudnativecon
----
-
-<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
-
-The good old baseline is "iam an an developer, i write code - now i have to do stuff to continue writing code".
-Most developers will continue on to "now i have to write scripts" on order to just do their jobs instead of working on infra.
-
-These scripts evolve to tools which evolve into an internal platform (if everyone starts using it).
-Other base components can also feel like platforms (for example application servers).
-
-## The early day evolution
-
-- Hudson
-- Docker: Not really building platforms, rather standardized application packaging
-- Kubernetes (and Nomad + Swarm): A new concept of scheduling instead of jsut running the application in a container
-
-=> We've been building platforms (or failing to build them) for years and years but now we kinda agree about what a platform is
-
-## Present
-
-We have the base idea of a platform
-
-```mermaid
-graph LR
-    ServiceConsumers-->|Consume through|HTTPAPI-->|Trigger work on|Controllers-->|So|Services
-    ServiceOwner-->|Manages|Services
-```
-
-- The fist question: Do we use public controllers (e.g. the cncf landscape projects) or build our own?
-- Result: Mostly a mix starting with public, realizing needs and expanding
-
-## Make it your own
-
-- Goal: Make the platform domain specific for your developers
-- Evolution: Tools like DAPR for developers or Crossplane for api-building
-- Build the API and Controllers first - dashboard, gitops, observability, ... second
-- Remember that kubernetes can manage anything - not just containers
-
-TODO: Steal image
-
-## Blueprints
-
-Take all of the projects you need, combine them and hide the complexity
-High level architecture of internal platforms is the same as public ones (aws, ...) but internal and built on kubernetes.
-
-TODO: Steal images for platform blueprints (3 slides)
-
-## Future
-
-- Platform Engineering certification by the CNCF is on the horizon
-- Do we need to hide kubernetes from developers? Maybe -> The CNCF is starting groups to get app devs closer to platform engineers
-- More multi-cluster specialized tools are sprawling in the last year (scheduling, discovery, management)
-- AI things are happening and we should utilize it but not just by calling a llm directly and calling it a day -> e.g. dapr llm abstraction api
-- Platforms are not built in isolation, we need to help each other

content/day0/_index.md

@@ -9,9 +9,8 @@ This year I spent most of my time at the platform engineering day.
 
 ## Talk recommendations
 
-- [So you want to hire for platform engineering](../06_hire-engineers)
+- TODO:
-- [The past, the present and the future of platform engineering](../07_past-present-future)
 
 ## Other stuff I learned or people i talk to
 
-- Meshcloud: They build developer platform tooling (currently mostly integrated with cloud providers)
+- TODO:

content/day0/talk.md

@@ -0,0 +1,10 @@
+---
+title: Title
+weight: <index of talk on the day>
+tags:
+ - <tag>
+---
+
+<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
+
+TODO: