Platform engineering has been a core theme with in cloud native community for last couple of years. Thanks for highlighting the systemic scalability and complexity challenges in platform engineering today. The CVE for availability is an interesting solution and could be a breakthrough in taming endemic complexity and human bottlenecks.
Platform teams need a delightfully different approach, not one that sucks less
11–14 of 14 posts
Re: Platform teams need a delightfully different approach, not one that sucks less
#12I'm curious about how the platform team approaches continuous learning and knowledge acquisition. Do they rely solely on post-mortems and incidents, or do they also incorporate insights from training? Are there any benchmarks for success? Thank you so much for sharing the article; I really appreciate the presentation and concise description of the platform
Most are just focusing on incident response and reactively improving things. That's why a proactive discipline that prevents these issues from happening is dearly missed.
Even when postmortems are done, information continues to exist in team silos as there is no way to share these learning across teams and enterprises. Hence, everyone repeats each others' mistakes.
Re: Platform teams need a delightfully different approach, not one that sucks less
#13I thought we were the only ones that had these issues :) I wonder how other teams are solving the hiring vs automation challenges?
Mostly by hiring contractors, which is basically not working well for a lot of enterprises.
Re: Platform teams need a delightfully different approach, not one that sucks less
#14Thank you for sharing insights into the burning issues of platform engineers. Cloud complexity is an old problem that requires new solutions. Standardization and knowledge sharing will save both time and efforts. Good luck
Thanks! Indeed, sharing knowledge programmatically will save time and effort, _while_ improving safety of these systems.