jspaw

It’d be amazing if it could calculate the cost of the consequences of not having a meeting which, in hindsight, would have been less costly.

Not saying it’s common, but those situations do exist.

It seems the results (knowledge silos, review cliques, and rubber stamping) would be inaccurate often since the heuristics can’t actually capture what they say they do? I would be concerned about users not having much faith in it once it returns one too many false signals.

“Again, these are just assertions. I’m less invested in some of these than I’m presenting. The talk isn’t about any one of them. I’m not here to convince you that my reflections are valid. This is about the exercise of discussing and questioning.”

Thanks for the feedback!

The hindsight bias is a helluva drug.

Hoping the author of that page sees: https://youtu.be/TqaFT-0cY7U

It’s news article titles like “Reckless American 777 Pilots Refuse Recorded NTSB Interviews” that fuel this sort of pushback that the pilots are giving about interviews.

NTSB investigative materials are not ‘privileged’ in the same way accident investigations in the US DOD are (https://medium.com/code-for-america/john-allspaw-getting-the...) but perhaps they ought to be.

Hindsight is a helluva drug. The SEC report cannot be viewed as a “postmortem.”

https://www.kitchensoap.com/2013/10/29/counterfactuals-knigh...

The SRE book authors cited the post specifically (https://sre.google/sre-book/bibliography/#All12), and Googlers I’ve spoken to mentioned its influence there.

I coined this term (https://codeascraft.com/2012/05/22/blameless-postmortems/) and believe (productive and earnest) critique can be valuable when it comes to terms like this one. (See also “devops”, “agile”, “serverless”, “toil”, “technical debt”, and others)

Paul Reed has made a great case for ‘blame-aware’ (https://medium.com/@jpaulreed/why-blameless-postmortems-migh...)

Rein Henrichs also explores the topic very well through a unique lens (https://youtu.be/KXrsvLMqF1Q)

As Cipriani points out, there is the term and there is the concept(s) the term is intended to convey. It does seem to me more folks know the term than have read the origin (my post above from 2012). This is fine, as long as productive dialogue continues in the industry about what the term was made to convey.

A level floor doesn’t have influence on the table being flat?

Does the observer’s perspective being parallel with the table’s surface have anything to do with it?

When viewed through a microscope, is it “flat”?

Cause is constructed not objectively and comprehensively identified.

No, they can’t. Both approaches are linear and sequential chains of cause/effect, which do not work with complex adaptive systems.

Five whys give a cherry-picked paucity of data in an investigation: https://www.oreilly.com/ideas/the-infinite-hows

(see my post above) :)

It's multithreaded, so can take advantage of more CPU mores, unlike squid.

It has total disk cache persistence, so it won't lose any cache if the server crashes, traffic server crashes, unlike varnish.

If you've got cache spread over multiple spindles and one of the spindles dies while in production, it'll just keep on going, skipping that spindle. Squid does this, varnish does not.

It does run on linux. Actually it's what it was built on, originally, IIRC.

I have used TrafficServer (at Yahoo) and I'm willing to bet that it will overtake both squid and varnish as time goes on.