This message was deleted.

Add there analytical skills and techniques :) we focus too much on tech part of Platform Engineering, but IDP, just like any other IT project - should start with functional & systems analysis (cognitive load recognition). —> https://khalasa.com/2024/01/how-to-approach-internal-developer-platform-delivery/

Looks cool @Nimesha Jinarajadasa, we are actually building an official platform engineering community version of something similar. @Krzysztof H. is right that the key thing missed here is the strong emphasis on the “theoretical” part. Platform engineering is much more than a technical shift, it’s a shift in mentality and ways of working as well.

Yup, people and communication are a big part of the success regardless of the method.

Thanks a lot.. @Luca Galante After conducting thorough research, We have developed a Platform Engineering Guide at KodeKloud. Have a look and let me know what do you think about it https://docs.google.com/viewer?url=https://raw.githubusercontent.com/kodekloudhub/de[…]n/Platform%20Engineering/Platform%20Engineering%20Roadmap.pdf Github Download link: https://github.com/kodekloudhub/devops-101/tree/main/Platform%20Engineering

Just a few thoughts, after skimming - will need to find time for a thorough read • PDF as delivery format is not contribution friendly • You might want to rethink the order of things in your roadmap ◦ Softskills last? ◦ Programming as second step, before you learned how to actually have the things you want to automate? • You might want to refresh your tech diagram on page three with the options from here - e.g. marketing likes that you push Humanitec as the only orchestrator, but there is choice out there 🙂

Thanks Your feedback is helpful!

I like this, does a good job of laying out what I think a Platform team should do without being too prescriptive. I would point out that Kubernetes is not the only container orchestration tool out there. Too often there is an assumption that Platform == Kubernetes.