[chrisdirkis]

I'll note, for the purpose of discussion, that this is put forth as part of an example engineering strategy document. The author does not recommend _the reader_ do this, at least not here.

With that said, yeah, I think "a static ratio" vs "a flat count based on desired features" vs something else is an interesting discussion! My experience is that more product means more usage of the breadth of infrastructure, and requires both more infra development and more support, but I haven't worked in large orgs, so I don't know how this nets out as size grows.

[kodah]

I was commenting from the perspective of a large org, thinking of one big enough that would need a strategy. You don't differentiate product and infra spaces, because infra is part of the product. It's at least well known in SRE spaces that SREs don't scale linearly with product. You generally build teams around specific needs and productize things that enable that non-linearness.