Replies

This profile is from a federated server and may be incomplete. Browse more on the original instance.

norootcause, to random
@norootcause@hachyderm.io avatar

Data should always be used to inform judgment, never to replace it.

norootcause,
@norootcause@hachyderm.io avatar

@joshourisman There’s a reason he never made captain.

norootcause, to random
@norootcause@hachyderm.io avatar

“Ethernet” is a great name.

norootcause,
@norootcause@hachyderm.io avatar

“Wi-fi”, on the other hand, is way too cutesy.

igb, to random
@igb@mastodon.hccp.org avatar

Did you know the interior of the average oven door can hold up to as much as 2 ounces of fully cooked dal?

It’s true. The trick, as I’ve discovered, is to make sure the dal is evenly distributed throughout the interior of the oven door and between as many layers of oven door window glass as possible.

norootcause,
@norootcause@hachyderm.io avatar

@igb This sounds like hard-won knowledge

norootcause, to random
@norootcause@hachyderm.io avatar

I enjoy seeing the Slack workaround of people changing their handle to indicate when they are OOO. Even though Slack has first-class support for indicating status, people still find the handle rename a useful way to transmit this info.

norootcause,
@norootcause@hachyderm.io avatar

@grimalkina I do appreciate how Slack decoupled your handle from your identity, so you can easily change your handle. Allowing different identities to use the same handle is an… interesting design decision.

norootcause, to random
@norootcause@hachyderm.io avatar

It's funny that we say "in lieu of" instead of "in place of" given that "lieu" is French for "place". I guess we're saving a letter?

norootcause,
@norootcause@hachyderm.io avatar

@jpmens That is the only way I have heard it pronounced by English speakers!

norootcause,
@norootcause@hachyderm.io avatar

@jpmens I heard it often in my youth growing up in Quebec!

norootcause, to random
@norootcause@hachyderm.io avatar

Everyone is always resource constrained.

norootcause,
@norootcause@hachyderm.io avatar

@coldclimate The most precious of resources!

jpmens, to random
@jpmens@mastodon.social avatar

deleted_by_author

  • Loading...
  • norootcause,
    @norootcause@hachyderm.io avatar

    @jpmens 404? More like 410.

    norootcause, to random
    @norootcause@hachyderm.io avatar

    I don't care about MTTR, I care about TCI (total cost of incidents).

    norootcause,
    @norootcause@hachyderm.io avatar

    @kellogh You totally should!

    norootcause, to random
    @norootcause@hachyderm.io avatar
    norootcause,
    @norootcause@hachyderm.io avatar

    In particular, I think the authors miss the risk of automated mitigation approaches creating new failure modes.

    c.f. https://surfingcomplexity.blog/2017/06/24/a-conjecture-on-why-reliable-systems-fail/

    norootcause,
    @norootcause@hachyderm.io avatar

    @hazelweakly Ashby wept.

    norootcause, to random
    @norootcause@hachyderm.io avatar

    Wait, Redis is pronounced “reed-is”? I’ve been saying “red-is” the whole time!

    norootcause,
    @norootcause@hachyderm.io avatar
    norootcause, to random
    @norootcause@hachyderm.io avatar
    norootcause,
    @norootcause@hachyderm.io avatar

    @hazelweakly Yeah, I haven’t really seen good patterns for making invariants first-class entities and running checks against them on a regular basis.

    norootcause,
    @norootcause@hachyderm.io avatar

    @stuartmarks @regehr I thought of that sort of harsh reaction as I was reading this line from the book "Behind Human Error":

    > To say that something should have been obvious when it manifestly was not, may reveal more about our ignorance of the demands and activities of this complex world than it does about the performance its practitioners.

    hazelweakly, to random
    @hazelweakly@hachyderm.io avatar

    Pretty much all of the woes of distributed tracing are caused from the mismatch of the mental model of distributed tracing that makes sense vs the one that can be built easily:

    The model that makes sense is "lazily built and incrementally fleshed out call graph with late-binding updates of attributes as discovered"

    But the way that makes sense to implement it is "strict call-stack semantics with fire-and-forget frozen rows of data into an append only data store"

    norootcause,
    @norootcause@hachyderm.io avatar

    @hazelweakly I think your observation that:

    “Pretty much all of the woes of X are caused from the mismatch of the mental model of X that makes sense vs the one that can be built easily.”

    holds for multiple values of X

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • khanakhh
  • kavyap
  • thenastyranch
  • everett
  • tacticalgear
  • rosin
  • Durango
  • DreamBathrooms
  • mdbf
  • magazineikmin
  • InstantRegret
  • Youngstown
  • slotface
  • megavids
  • ethstaker
  • ngwrru68w68
  • cisconetworking
  • modclub
  • tester
  • osvaldo12
  • cubers
  • GTA5RPClips
  • normalnudes
  • Leos
  • provamag3
  • anitta
  • lostlight
  • All magazines