| ▲ | rubiquity 5 hours ago | ||||||||||||||||||||||
Nice I started a timer for how quickly a "well actually, SRE at google" would show up and you did not fail to deliver. > The point of SRE is to have a team dedicated to scaling/resilience to balance the tension between product pushing to ship features. Sounds like a cultural issue. Google should look into that. | |||||||||||||||||||||||
| ▲ | RexySaxMan 4 hours ago | parent | next [-] | ||||||||||||||||||||||
Why is your response so pithy? Google invented the term SRE, and I think how they use SRE is pretty relevant to the discussion. | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | ImPostingOnHN 5 hours ago | parent | prev | next [-] | ||||||||||||||||||||||
It turns out it's easier to hire people who specialize in scalability, reliability, debugging of distributed complex systems, cost ops, efficiency gains, etc. than it is to instantly ensure every single engineer that works there is an expert in all those things, without anybody on staff who is an expert in them. Much like database skills, IT security skills, etc. It's still something everyone can theoretically learn, of course, and someone who works in that role is most effective by instilling those disciplines in others as they go, and making everyone successful. | |||||||||||||||||||||||
| ▲ | hparadiz 5 hours ago | parent | prev | next [-] | ||||||||||||||||||||||
He's right you know. | |||||||||||||||||||||||
| ▲ | unethical_ban 4 hours ago | parent | prev [-] | ||||||||||||||||||||||
A cultural issue that many organizations face. Same reason most large companies have an infosec department that runs separately from IT. | |||||||||||||||||||||||