jspaw

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.

Comment · 8 years ago

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.

Comment · 8 years ago

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

Comment · 16 years ago

(see my post above) :)

Comment · 16 years ago

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.