https://platformengineering.org logo
Join Slack
Powered by
I don’t tend to share articles from our platform e...
# general
s
I don’t tend to share articles from our platform engineering blog - but this one has really resonated. It’s crazy watching the reads pour in! I’m curious what everyone here’s thoughts are? https://platformengineering.org/blog/why-platform-engineering-will-eat-the-world
I’m curious your perspective on the article @Jordan Chernev - did you see this kind of process at Wayfair?
j
i just skimmed the article. i didn’t quite catch a “process” part in it… in terms of ratios, we were probably closer to 1:10, maybe 1:12
in terms of role breakdown, we did have all but the OPE in either name or concept
in retrospect, i think that level of granularity is probably less of a concern / focus and instead, we should focus more on overall team composition, i.e. software skillset vs systems skillset (reliability can go in here too)
my canonical example is the logging team we built from scratch which was nearly a 50:50 ratio of software:systems personnel. that team is the mental template i use to build platform teams / functions
s
Super interesting. Thank you. By process I meant more that as the platform expands and advances it starts to absorb other historically distinct disciplines like security or SRE.
j
we were logically operating in that configuration, just not formally from an org design perspective. please think cross-functional tiger teams with shared roadmaps and/or embedded personnel
s
Makes perfect sense. Do you think over a few more years that informal configuration would have become formal?
j
hard to tell. maybe yes on the devsecops arm in security (but not Risk, Compliance, SOC, etc). SRE is more murkier but that’s because of cultural, alignment and budgetary choices made at wayfair historically. those feel difficult to unwind easily but certainly not impossible
Open in Slack
PreviousNext
Powered by