This message was deleted.
# generals
Slackbot
05/18/2023, 4:38 PMThis message was deleted.
r
Ron Cuirle
05/18/2023, 6:42 PMQuestion 1. Sometimes. But we may have different definitions of workflow. Do you have an example of a workflow that you sense can/should be "platformized?" (patent pending 🙂 )
z
Zahi Ben Shabat
05/18/2023, 8:22 PMr
Rajesh Gupta
05/19/2023, 9:14 AMQ1: Yes, I have the same feeling. To me, platform engineering is an emerging trend that is going to go hand-in-hand in the future supporting DevOps within an organization to speed-up go to market of your services.
Q2: Yes, very much interested.
r
Romaric Philogène
05/19/2023, 9:45 AM@Ron Cuirle an idea would be to take a traditional DevOps tech stack (E.g. Kubernetes + ArgoCD ) and turn it into a “Platform Engineering” mindset stack. How to make developers use this stack with the appropriate developer experience. It’s just an example but we can apply this one to multiple examples.
Romaric Philogène
05/19/2023, 9:47 AM@Zahi Ben Shabat Backstage could be interesting to explore as well. I think it aligns well with the Platform Engineering methodology even if I am not super fan of it : )
r
Ron Cuirle
05/19/2023, 1:02 PMOur approach at Shipt has been a singular developer interface (UI and CLI). Similar to Backstage. Everything is exposed through it - even if they're just links to other systems. Devs follow along from git commit to running in prod. They don't have to take action in between. The primary way to establish a platform mindset is to treat the platform like a product. Microsoft Office isn't really a product; it's a suite. People experience "Office" whether they're using Word or Excel.
8 Views