I said nothing different, though you could interpret it this way. I agree with your point. We managed to ruin another good idea by inventing some certificates and new job titles.

Hm, I was arguing this point: > if you have DevOps engineers, you don't do DevOps. I think those points are more or less unrelated.

An oversimplification because it correlated pretty often in my experience. You are right, not related.

👍🙂

To me SRE is the evolution of what had been the typical setup of IT ops and app management in cloud environments. You simply do not need a ops team who mimic an internal cloud vendor but the same shift in mindset for app management that should have happened on the dev side.

I think there are multiple points: - Not everything Google does makes sense for others. Google has a very huge scale. I think that is a good point. - SREs probably don't make sense outside Google. I am not sure why and would tend to disagree.

- SRE *teams* don't make sense outside Google because scale. I am not sure whether SREs imply a separate team - you probably can have just one SRE.

I spoke to @spanneberg who did SRE @InstanaHQ . Seemed to have worked well. software-architektur.tv/2021…

In hindsight, mixing SRE into this tweet was an oversimplification and a mistake. Sorry for this.

No problem. I have to admit that I am not fully comfortable discussing tweets in very fine detail. At the end, I myself do quite a few tweets quickly and that is part of the fun. And of course I do embarrassing errors in the process.