4 ms·

> Sorry, I'm merely a lowly sysadmin and not a godly Google SRE Don't really like how this is framed - plenty of Google SREs are born and bred sysadmins.

• dijit 7y ago
  My comment was a bit flippant I agree, and I know Google is a huge company so there are a great many people I have never interacted with. That said; the google approach _does_ appear to quite literally throw away institutional knowledge from high throughput/high uptime and automation focused systems engineering. I don’t discount that google SREs are highly intelligent and often know systems internals to the same or a greater extent than highly performing sysadmins. But there does appear to be desire to discredit anything seen as “traditional” and I think that can be harmful, like in this case. Sometimes they know better, but there is a failing to ask the question: “what does it cost to only act on symptoms not causes”
  • cameronbrown 7y ago
    > Sometimes they know better, but there is a failing to ask the question: “what does it cost to only act on symptoms not causes” I imagine hardware breaking is the cost -- but as long as an engineer's time is worth more than the hardware, that tradeoff will be made.
    • tjoff 7y ago
      Debugging and replacing is far more time consuming and costly, both in hardware money and engineer money.