@mononcqc@hachyderm.io
@mononcqc@hachyderm.io avatar

mononcqc

@mononcqc@hachyderm.io

Staff SRE @ honeycomb.io, Tech Book Author, Erlang Ecosystem Foundation co-founder, Resilience Engineering fan. SRE-not-sorry.

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

grimalkina, to random
@grimalkina@mastodon.social avatar

I stumbled across this post while looking for our workbook and omg! What a very thoughtful and understanding summary of our code review anxiety paper, model, and takeaways. I don't know this person to tag them but 👏👏👏

https://ferd.ca/notes/paper-understanding-and-effectively-mitigating-code-review-anxiety.html

mononcqc,
@mononcqc@hachyderm.io avatar

@grimalkina you apparently follow me on here already ;)

I think you may like to hear that I used the paper (shared to me by @RainofTerra) as an inspiration for a discussion session with our on-call engineers titled “Can Stress, Fear, and Anxiety be useful in Ops, and if so, when?”—just hoping to make room for the topic.

We ended up having a few people commenting along the lines of “I’m so glad to hear this isn’t just a ‘me’ problem,” which is great.

mononcqc, to random
@mononcqc@hachyderm.io avatar

"AI is actually gonna be great any time now," I tell myself as everything that was somewhat usable gets generative AI wedged into it in the most unhelpful ways possible time and time again

mononcqc,
@mononcqc@hachyderm.io avatar

@hazelweakly the torment nexus has been democratized and made more easily applicable to vast populations, albeit in a less thorough manner.

mononcqc, to random
@mononcqc@hachyderm.io avatar
mononcqc, to programming
@mononcqc@hachyderm.io avatar

Good blog post from the team on optimizations coming in Erlang/OTP 27: https://www.erlang.org/blog/optimizations/

mononcqc, to random
@mononcqc@hachyderm.io avatar

This week’s is Understanding and Effectively Mitigating Code Review Anxiety by Carol S. Lee and Catherine M. Hicks: https://osf.io/preprints/psyarxiv/8k5a4

They developed a framework and intervention around code review anxiety based on research about social anxiety, ran a study validating it, and created a model of key metrics that influence code review avoidance that was also shown to be helped by a single workshop intervention.

Notes at https://ferd.ca/notes/paper-understanding-and-effectively-mitigating-code-review-anxiety.html and https://cohost.org/mononcqc/post/5656626-paper-understanding

mononcqc, to random
@mononcqc@hachyderm.io avatar

The folks at InfoQ published (and transcribed!) the talk I gave at QCon New York in June 2023—Embrace Complexity; Tighten Your Feedback Loops—and is now available at: https://www.infoq.com/presentations/complexity-feedback-loops/

I also have a text version on my blog at https://ferd.ca/embrace-complexity-tighten-your-feedback-loops.html.

mononcqc,
@mononcqc@hachyderm.io avatar

@tef the real title is "this is all going to hell anyway; all we can do is influence how long it's gonna take" at least, which is more honest

mononcqc, to programming
@mononcqc@hachyderm.io avatar

If anyone in the community has been using the rich compiler error option in Rebar3 over the last year, I’m looking for any feedback or opposition before turning it on by default in the next release: https://github.com/erlang/rebar3/pull/2881

hazelweakly, to random
@hazelweakly@hachyderm.io avatar

I swear, so much complexity of my life right now comes from me wanting to be able to graphically draw out an interconnected hypergraph but also have a convenient textual representation of said hypergraph

I'm sure this makes zero sense to people. But ugh. It's so frustrating to have the ideas in your brain and just not be able to really tease them out in a useful way for others

Signed,
trying to figure out how to map "do the platform engineering thing more better" into strategy and architecture

mononcqc,
@mononcqc@hachyderm.io avatar

@hazelweakly @adrianco this might be a sensemaking/analysis distinction?

In complex landscapes, a complex map is going to be of little help to people who aren't experts at reading the map.

Maps are models, so it may be worth making multiple maps for multiple purposes and dedicated lenses/perspectives, usable in distinct contexts.

(analogy: aeronautical charts, topographic maps, demographic maps, and road maps may all be connected but are distinct as contextual usage outperforms completeness)

mononcqc, to random
@mononcqc@hachyderm.io avatar

A few days ago, @hazelweakly wrote about her redefinition of observability on her blog.

I decided to add some extra color commentary to it on mine, in an attempt to provide extra context and framing around her ideas, but also around classical definitions of observability.

The post covers differences between insights and questions, distinctions between observability and data availability, socio-technical implications, mapping complex systems, and on the use of models.

https://ferd.ca/a-commentary-on-defining-observability.html

mononcqc,
@mononcqc@hachyderm.io avatar

@norootcause @hazelweakly be the older school hobbyist web you want to see, or something to that effect.

mononcqc, to random
@mononcqc@hachyderm.io avatar

A blog post I wrote has been published at work: https://www.honeycomb.io/blog/negotiating-priorities-incident-investigations

It describes the types of incident investigations that exist (according to Dekker) and how we use multiple reports to try and satisfy distinct and often clashing purposes for different stakeholders.

mononcqc, to random
@mononcqc@hachyderm.io avatar

When people discuss blame around automation harming someone, a common issue is a person having broken a procedure or rule.

Blame is often attributed right away—it’s their fault.

I find it useful to ask “is it common/necessary/practical for people to bend or ignore the rule?”

If the answer is “yes” or even ambiguous, then maybe you should also wonder whether it is the automation (and/or the procedures) that aren’t adequate, rather than the people involved.

mononcqc, to random
@mononcqc@hachyderm.io avatar

I grabbed a bunch of old notes and turned them into an intro blog post giving a quick overview of distributed systems fundamentals: https://ferd.ca/a-distributed-systems-reading-list.html

mononcqc, to random
@mononcqc@hachyderm.io avatar

This week's is Observation and assessment of crossing situations between pleasure craft and a small passenger ferry, which asks the question Can we get ready for automation by studying non-automated systems?

Paper at: https://link.springer.com/article/10.1007/s13437-020-00211-1

Notes at https://ferd.ca/notes/paper-observation-and-assessment-of-crossing-situations-between-pleasure-craft-and-a-small-passenger-ferry.html & https://cohost.org/mononcqc/post/4365540-paper-observation-a

mononcqc, to random
@mononcqc@hachyderm.io avatar

me: there is no reason why I would write more software, each new line of code is a burden I seek to avoid.

also me: why yes I will use the bespoke slideshow software I wrote for fun for my next presentation, I just need to make sure it still runs fine on the newer runtimes and OS versions and—

mononcqc, to random
@mononcqc@hachyderm.io avatar

Have you ever heard of Quebec’s pain sandwich (literally: “bread sandwich”), which is a “traditional” holiday meal from the 1920s and popularized until the 1940s (chicken spread, ham spread, and egg salad on bread cut on its length, then coated in either cheez whiz or philadelphia cheese) that few really like anymore, but that people keep making partly out of nostalgia.

Anyway one of our relatives makes the most outrageous one you can imagine, it’s a decently palatable horror show.

Slices of pain sandwich on plates.

mononcqc, to random
@mononcqc@hachyderm.io avatar

New blog post today: https://ferd.ca/negotiable-abstractions.html

In which I rant a bit about how factors entirely unrelated to code can drive change and define abstractions, and how these changes in turn can end up re-defining the context in which the code runs, which in turn prompts re-framing the software itself.

Basically, why I believe abstractions are contextual, subjective, and therefore negotiable.

mononcqc, to random
@mononcqc@hachyderm.io avatar

It's the time of the year where Home Alone is on TV or on people's streaming lists as the holidays classic it is.

That means it's also the time of the year where I dust off this incident review of it, before we all blame the movie's parents for being irresponsible: https://ferd.ca/home-alone-a-post-incident-review.html

mononcqc, to random
@mononcqc@hachyderm.io avatar

Posted up some notes on a transcript from NPR about why doctors still use pagers, and something they drop in called RHIP (Risk/Habit/Identity/Power).

Original transcript at https://www.npr.org/transcripts/1197955913

Notes at https://ferd.ca/notes/rhip-doctors-and-pagers.html and https://cohost.org/mononcqc/post/3892375-rhip-doctors-and-p

mononcqc, to random
@mononcqc@hachyderm.io avatar

Today's is " Visualizing Uncertainty for Non-Expert End Users: The Challenge of the Deterministic Construal Error"

https://www.frontiersin.org/articles/10.3389/fcomp.2020.590232/full

They try to identify the best way to visualize uncertainty in weather forecast and mostly come to the conclusion that only text really works?

Notes at https://ferd.ca/notes/paper-visualizing-uncertainty-for-non-expert-end-users.html and https://cohost.org/mononcqc/post/3822487-paper-visualizing-u

mononcqc, to random
@mononcqc@hachyderm.io avatar

Today's is "Workarounds to Computer Access in Healthcare Organizations: You Want My Password or a Dead Patient?"

https://www.cs.dartmouth.edu/~sws/pubs/ksbk15-draft.pdf

It's an ethnographic study of hospital systems and the ways in which IT security policies clash with real work, and the ways with which healthcare workers find to subvert and work around them.

Notes at https://ferd.ca/notes/paper-you-want-my-password-or-a-dead-patient.html & https://cohost.org/mononcqc/post/3647311-paper-you-want-my-p

mononcqc, to random
@mononcqc@hachyderm.io avatar

From a Reuters article:

> OpenAI defines AGI as autonomous systems that surpass humans in most economically valuable tasks.

This is such an incredibly bad definition from OpenAI that hours after reading it I still can't believe they'd pick something so bad.

prosperity gospel-ass definition that fully lines up with the brainwormy tech shit effective altruists seem to keep churning out though, so sure why not.

mononcqc, to random
@mononcqc@hachyderm.io avatar

I keep turning these rocks and I keep finding bugs under them, what the hell

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