diff --git a/content/_index.md b/content/_index.md index ea48981..dbb4bad 100644 --- a/content/_index.md +++ b/content/_index.md @@ -10,6 +10,7 @@ This is what typing the notes blindly in real time get's you. Every year I tell myself that I will fix them afterwards: To be fair I fix most of them but not all and that's fine. Also the notes tend to start out strong early in the week (aka Rejekts + CloudNativeCon) and fall off in terms of density and depth. +This also happens on a daily basis as soon as my brain starts to overflow with information (but not as noticable until late in the day) ## How did I get there? @@ -19,7 +20,8 @@ Why? Because learning about all new things in the world of cloud is really impor I enjoyed [last year's experience](https://kubecon25.nicolai-ort.com) and [the year before](https://kubecon25.nicolai-ort.com), so I wanted to go again. And I managed to get a free ticket by being accepted as a speaker at the Platform Engineering Day Europe 2026 🥳. -(Alto I already convinced my business parter that the company would pay for my ticket before I got the news) +(Although I already convinced my business parter that the company would pay for my ticket before I got the news) +So I was there proudly representing ODIT.Services. ## And how does this website get it's content diff --git a/content/day0/10_sourcing-your-idp.md b/content/day0/10_sourcing-your-idp.md new file mode 100644 index 0000000..24f5096 --- /dev/null +++ b/content/day0/10_sourcing-your-idp.md @@ -0,0 +1,88 @@ +--- +title: "A Practical Guide To Inner Sourcing Your IDP" +weight: 10 +tags: + - platformengineeringday + - platform + - idp +--- + + +{{% button href="https://www.canva.com/design/DAHBlkrzYH8/ZSe4SkJVGy8GnMtDcCGdHw/view?utm_content=DAHBlkrzYH8&utm_campaign=designshare&utm_medium=link2&utm_source=uniquelinks&utlId=h86fe2f7313" style="tip" icon="person-chalkboard" %}}Slides{{% /button %}} + +{{% button href="https://lianmakesthings.dev" style="info" icon="link" %}}Homepage{{% /button %}} +{{% button href="https://devrelbook.com" style="info" icon="link" %}}Dev Rel{{% /button %}} + +A talk by Lian and i can always recommend her talks. + +## Background + +- 55% of orgs have adopted but only 27% have integrated best practives -> They built technically impressive ghost towns +- We're not good at explaining/thinking about platforms -> Viewing them as a whole house instead of the collection of bricks that make them up +- The deployment process evolved from scripts to services (shared scripts) to platforms (shared scripts with extra steps) +- Platform adoption is not a technical but an advocacy problem +- Idea: Treat the platform to as a shared project -> We need devrel (Dicover evaluate learn build scale) + +TODO: Steal lian's evolution slide + +## Case studies + +### A + +- Base: Buerocratic and individual driven with general apahty due to frequent objective changes but with individual heroes +- Ideas: + - Internal user groups (low contribution ight amount of complaints) + - CI Librarbies (that no one used) + - A pilot program -> Actually works + +### B + +- Large manufacturer, mission driven but tool anarchy and a buch of sub-cultures +- Collection: +- Diagnosys: + +## The platform advocacy framework + +- Goal: Turn passive users into passionate advocates +- Based on: CNCF platform maturity model + - Levels: Provisional, Operational (Dedicated Team+Budget), Scalable (Grow without diusruptions), Optimizing (Anticipate needs/changes) + - Aspects: Investment, Adoption, Interfaces, Operations, Measurement -> Aspect levels are indipendent from one another +- Potential Trap: Creating actions just to graduate to the next level without actually keeping cultiure in mind +- The orbit model: + - Love: Activity in the community + - Reach: Ability to pull others with you + - Risk: Only focussing on high reach+love but the peopple with the most valuable feedback are usually hrll or lrll +- Tribal Culture + - Stages: Life Sucks -> My Life Sucks (Victim of the system mindset) -> I'm great - no you are not (lone warrior) -> We are great (mission driven) -> Life is great (team driven) + - You have to move from one stage to another, no skipping + +### CNCF Platform maturity + +TODO: Copy from slide + +### Orbit model + + +TODO: Make readable +| | Low Love | High Love | +| - | - | - | + +Low Reach/Love: Detached observer Contractors, Juniors +Low Reach/high love: Indipendent Fans Early adopters, individual contributor +HR /ll: Sceptics (Managers, Architects, CTOs) +HR/HL: Exoert multipliers (Senior ICs, Internal Advocates, Platform champoins) + +### Tribal Culture model + +TODO: Beautify the text above + +## Using the framework + +- Culture first -> The culture sets your options and limits +- Cycle: + 1. Collect data (Use the three discussed maturity models) + 2. Analyse bottlenecks/root causes (Keep with the DevRel journey) + 3. Invervene: Decide on actions and take them (sientific method style: hypothesis -> define action -> define success metric and threshhold -> take action -> compare desired outcome) + 4. Repeat +- Important: Requires patience if it's hard to show the value or missing value in numbers +- Innersourcing moves the platform from the team into the whole org \ No newline at end of file diff --git a/content/day0/_index.md b/content/day0/_index.md index 4884d9a..f1ee49b 100644 --- a/content/day0/_index.md +++ b/content/day0/_index.md @@ -12,6 +12,7 @@ This day also included my highlight of the conference (I'm writing this on the s ## Talk recommendations - [Who built this platform? Alternative viewpoints on Platform Design](./03_whobuiltthis) +- [A Practical Guide To Inner Sourcing Your IDP](./10_sourcing-your-idp) ## Other stuff I learned or people i talk to