Platform engineering is the discipline of designing and building toolchains and workflows that enable self-service capabilities for software engineering organizations in the cloud-native era.

Platform Engineering

i am somewhere right in the middle.. the platform can serve legacy applications, but it's requires a solid amount of work from a team to migrate there.. we're trying to make a lot easier

Which Team ? platform? :) I think that migration is a job for platform or enabling Team. Making developers do it does not bring any value from business perspective. So the less of developers time spent on migration, the better! I recently also had a migration project and we tried to avoid involving the developers too much.
But it’s a separate topic - in this case I would say :two: 

current consensus seems to be :two:;  I also wonder why a company would invest in a platform strategy that doesn't take into consideration their current applications running in production?  Especially when the aim is to build golden paths through standardization and leveraging the right points of abstraction.

I was working for such a company in 2020-2022. Their IT Strategy was to limit the changes in existing systems &amp; build microservice-based new solutions instead - for most of the business domains. The legacy they had was really a blocker in terms of new features delivery, operations &amp; hiring

ah I see - that sounds like the strangler pattern for app modernization;  was the desire to eventually sunset the legacy systems in favor of the microservices-based solutions?

Yes, exactly - strangler pattern with a slow „death” of old solutions due to more &amp; more functionalities migrated to microservices :) 

<@U051DCBPVPG> yes i’m referring to the fact that it takes some work from other teams.  I would consider those teams to be stream aligned teams since they are building new products for the business.  It definitely does not create much value for the business overall in the short term for them to invest time is migrating to the new platform (but once they’re on it they get faster development velocity and reliability for everything they build!) 

we are working now to make the migration process easier.. that is a big job in itself because there are a number of different needs that a team that wants to migrate might have.. so lots of conversations and prioritization! 

Good luck <@U04DLDG736Z> ! If you need any help or a „rubber duck” with some IDP management experience, reach out to me :) 

There will always be a lot of asks coming from teams that use your idp. It’s critical that you make sure the ask is generic, applicable enterprise wide and serves more than just one niche need. Also they might come to you with a solution they want you to implement. Make sure they explain the pain point first! You might haready have a solution in place! 

these are great points <@U03LMPR7HPV>! I think if I can rephrase the asks to be generic, I will find there are not as many different needs than I think there are :thinking_face: 

yeah, that way you build a capability that maps to a business need and not a team's needs