News for hackers. Stuff that matters.
Re:Finding a problem at the bottom of the Google stack by dijit on Monday March 16, 2020 @07:38AM (#22591813)
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”

Re:Finding a problem at the bottom of the Google stack by cameronbrown on Monday March 16, 2020 @05:39PM (#22598198)
> 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.

Re:Finding a problem at the bottom of the Google stack by tjoff on Monday March 16, 2020 @05:55PM (#22598413)
Debugging and replacing is far more time consuming and costly, both in hardware money and engineer money.