docs(day0): Added abstractions
All checks were successful
Build latest image / build-container (push) Successful in 53s
All checks were successful
Build latest image / build-container (push) Successful in 53s
This commit is contained in:
parent
c09bf8f637
commit
f8512dc6ae
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Platform abstractions: Asset or liability
|
||||
title: "Platform abstractions: Asset or liability"
|
||||
weight: 10
|
||||
tags:
|
||||
- platform
|
||||
@ -72,4 +72,17 @@ TODO: Steal image
|
||||
|
||||
- Can teams access lower level controls (when needed) while staying with the abstraction
|
||||
- Do users understand what happens underneath (when needed)
|
||||
- Are ther documented extension/customization points?
|
||||
- Are ther documented extension/customization points?
|
||||
|
||||
## Patterns to break the debt trap
|
||||
|
||||
- Layered abstraction patterns: start with low-level abstractions that get abstracted on higher levels to allow users to choose the right abstraction level for themselves without having to configure everything themselfes
|
||||
- Expert-ap: Additional api parameters that are not needed but can be set
|
||||
- Policy based guard rails: Change the guardrails based on the environment (e.g. deep access in dev, not in prod)
|
||||
|
||||
## The end goal
|
||||
|
||||
- Increase adoption
|
||||
- Eliminate shadow IT
|
||||
- Improved satisfaction
|
||||
- Reduced overhead
|
@ -9,10 +9,11 @@ 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)
|
||||
- [The past, the present and the future of platform engineering](../07_past-present-future)
|
||||
- [Product thinking for cloud native engineers](../08_product-thinking)
|
||||
- [A million ways to promote changes between environments](../09_promotions)
|
||||
- How to design a good hireing process: [So you want to hire for platform engineering](../06_hire-engineers)
|
||||
- Evolution of Platforms and Platform Engineering: [The past, the present and the future of platform engineering](../07_past-present-future)
|
||||
- How to design a good product: [Product thinking for cloud native engineers](../08_product-thinking)
|
||||
- Staging with gitops: [A million ways to promote changes between environments](../09_promotions)
|
||||
- How to handle abstractions and new requriements: [Platform abstractions: Asset or liability](../10_abstractions)
|
||||
|
||||
## Other stuff I learned or people i talk to
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user