Computational Stress in Production

Last night I attended MiniCAST, an online version of the Association for Software Testing's famous CAST conference. I've never been to CAST in person but I can say that the vibe here was great, much more informal and peer-based than the presenter-audience split I've seen elsewhere. It ran for four hours and squeezed in four talks on two tracks, several socialising sessions, and a keynote from Rachel Kibler.

Rachel spoke about stress cases, those scenarios when context, or the product, or both in tandem distress the user. For example, the health-tracking app that excluded women because it didn't include menstrual cycles, or the social media app that pushed a daughter's photo into a dad's timeline with a celebratory whoop ... on the anniversary of her death, or the ride-share app with numerous pop-ups that is hard to use in the dark, walking fast, with low battery, trying to get a lift out of a bad neighbourhood.

These kinds of threats to inclusivity, emotional stability, and personal security are seen in development process with low diversity, a focus on success, and a lack of interest in users and their real life situations.

While not always common, stress cases should not be dismissed as simple edge cases (traditionally, a situation where some parameter is pushed to an extreme value). They affect real people in real, tangible, consequential ways. In our ROI-driven world this may not be enough of an argument for some software producers, but the potential for reputational damage probably is.

To help to avoid cases of stress in the wild, Rachel suggested a few approaches in development:

Have a designated dissenter, someone whose role is to look for the flaws, find the stress points, advocate for those who find themselves off the happy path.
Run pre-mortems, where the potential bad outcomes are written up as headlines and then routes to avoid them are found.
Read copy aloud in a bright voice. How does it sound when the content doesn't fit that medium?
Give some of your personas traumatic back history.
Put yourself under stress when testing. How does that feel? Where does the product fail (you)?
Be bold in telling management to be kind, considerate, and ethical.

Remember, there is no average user and someone is always having a bad day.

Sarah Aslanifar talked about computational thinking which she described as:

an iterative system of generative reasoning in which people build models of a subject in a notation capable of being executed objectively and automatically be a machine, with observable and falsifiable output.

This style of thinking is the result of a logical progression from concrete to abstract thought through human history: oral, written, and now computational. As I understood it, at each stage it was possible for there to be dialogue at a greater remove from reality and at a greater distance between participants.

We're in the computational phase now and our abstractions, or models, have the potential to be encoded and executed. Monte Carlo simulation, where scenarios are run numerous times to understand the space of possible outcomes from some starting situation and with some set of constraints, might be an example.

I don't think Sarah said it explicitly, but the key thing here seems to be the use of the computer as a tool to aid thinking. Exercising a model independently of our own heads gives us a chance to reflect on where it is successful and where it deviates from reality. Analysis of the results can help us to determine what to alter to try to make it better.

Machine learning seems like an interesting area of this space. It is notoriously hard to interrogate, although it is certainly possible to experiment with parameters to improve its outcomes. A generate-and-test strategy is reasonable for exploring an unknown area, but it's not clear to me that it would qualify as computational thinking, not least because of the falsifiability requirement in Sarah's definition.

Perhaps I should have asked Alex Eftimiades about that. He presented on the challenges and value of testing machine learning systems in production. Production for him is financial systems, and the goal of his work is to inspect the firehose of data looking for potentially fraudulent transactions.

One of the points he made early on was that in the "traditional" software testing world, there is a culture of binary pass/fail decisions, where a fail typically indicates some kind of bug. In the machine learning world that sharp distinction is smooshed out into a probability distribution where uncertainty around a result is the norm.

Without a guillotine oracle, the approaches open to testers are to question performance and divergences. These are still comparisons, because testing is about finding differences that make a difference, but they are now statistical in nature.

Without going into the technical weeds too much, Alex asked questions like does the performance of the system on its training and production data differ by an amount that is not explained by baseline variation? If I tweak the inputs to the system in known ways does the output of the system change in step in ways that are explainable and reasonable? Can I create a threshold for alerting by adjusting it until the balance of true and false positives is acceptable to me, in this context, at this time?

Comments

Meet Me Halfway?

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answ...

The Best Programmer Dan Knows

I was pairing with my friend Vernon at work last week, on a tool I've been developing. He was smiling broadly as I talked him through what I'd done because we've been here before. The tool facilitates a task that's time-consuming, inefficient, error-prone, tiresome, and important to get right. Vern knows that those kinds of factors trigger me to change or build something, and that's why he was struggling not to laugh out loud. He held himself together and asked a bunch of sensible questions about the need, the desired outcome, and the approach I'd taken. Then he mentioned a talk by Daniel Terhorst-North, called The Best Programmer I Know, and said that much of it paralleled what he sees me doing. It was my turn to laugh then, because I am not a good programmer, and I thought he knew that already. What I do accept, though, is that I am focussed on the value that programs can give, and getting some of that value as early as possible. He sent me a link to the ta...

How do I Test AI?

Recently a few people have asked me how I test AI. I'm happy to share my experiences, but I frame the question more broadly, perhaps something like this: what kinds of things do I consider when testing systems with artificial intelligence components . I freestyled liberally the first time I answered but when the question came up again I thought I'd write a few bullets to help me remember key things. This post is the latest iteration of that list. Caveats: I'm not an expert; what you see below is a reminder of things to pick up on during conversations so it's quite minimal; it's also messy; it's absolutely not a guide or a set of best practices; each point should be applied in context; the categories are very rough; it's certainly not complete. Also note that I work with teams who really know what they're doing on the domain, tech, and medical safety fronts and some of the things listed here are things they'd typically do some or all of. Testing ...

Beginning Sketchnoting

In September 2017 I attended Ian Johnson 's visual note-taking workshop at DDD East Anglia . For the rest of the day I made sketchnotes, including during Karo Stoltzenburg 's talk on exploratory testing for developers (sketch below), and since then I've been doing it on a regular basis. Karo recently asked whether I'd do a Team Eating (the Linguamatics brown bag lunch thing) on sketchnoting. I did, and this post captures some of what I said. Beginning sketchnoting, then. There's two sides to that: I still regard myself as a beginner at it, and today I'll give you some encouragement and some tips based on my experience, to begin sketchnoting for yourselves. I spend an enormous amount of time in situations where I find it helpful to take notes: testing, talking to colleagues about a problem, reading, 1-1 meetings, project meetings, workshops, conferences, and, and, and, and I could go on. I've long been interested in the approaches I've evol...

Don't Know? Find Out!

In What We Know We Don't Know , Hillel Wayne crisply summarises a handful of research findings about software development, describes how the research is carried out and reviewed and how he explores it, and contrasts those evidence-based results with the pronouncements of charismatic thought leaders. He also notes how and why this kind of research is hard in the software world. I won't pull much from the talk because I want to encourage you to watch it. Go on, it's reasonably short, it's comprehensible for me at 1.25x, and you can skip the section on Domain-Driven Design (the talk was at DDD Europe) if that's not your bag. Let me just give the same example that he opens with: research shows that most code reviews focus more on the first file presented to reviewers rather than the most important file in the eye of the developer. What we should learn: flag the starting and other critical files to receive more productive reviews. You never even thought about that possi...

My Adidas

If you've met me anywhere outside of a wedding or funeral, a snowy day, or a muddy field in the last 20 years you'll have seen me in Adidas Superstar trainers. But why? This post is for April Cools' Club . --00-- I'm the butt of many jokes in our house, but not having a good memory features prominently amongst them. See also being bald ("do you need a hat, Dad?"), wearing jeans that have elastane in them (they're very comfy but "oh look, he's got the jeggings on again!"), and finding joy in contorted puns ("no-one's laughing except you, you know that, right?") Which is why it's interesting that I have a very strong, if admittedly not complete, memory of the first time I heard Run DMC. Raising Hell , their third album, was released in the UK in May 1986 and I bought it pretty much immediately after hearing it on the evening show on Radio 1, probably presented by Janice Long, ...

Not a Happy Place

A few months ago I stopped having therapy because I felt I had stabilised myself enough to navigate life without it. For the time being, anyway. I'm sure the counselling helped me but I couldn't tell you how and I've chosen not to look deeply into it. For someone who is usually pretty analytical this is perhaps an interesting decision but I knew that I didn't want to be second-guessing my counsellor, Sue, or mentally cross-referencing stuff that I'd researched while we were talking. And talk was what we mostly did, with Sue suggesting hardly any specific tools for me to try. One that she did recommend was finding a happy place to visualise, somewhere that I could be out of the moment for a moment to calm disruptive thoughts. (Something like this .) Surprisingly, I found that I couldn't conjure anywhere up inside my head. That's when I realised that I've always had difficulty seeing with my mind's eye but never called it out. If I try to imagine ev...

Going Underground

The map is not the territory. You've heard this before and I've quoted it before . The longer quote (due to Alfred Korzybski) from which the snappy soundbite originated adds some valuable context: A map is not the territory it represents, but, if correct, it has a similar structure to the territory, which accounts for its usefulness. I was thinking about that this week as I came to a product new to me but quite mature with a very rich set of configuration options. When I say rich , I mean — without casting any shade, because I have been there and understand — it is set in multiple locations, has extensive potential effects, and is often difficult to understand. For my current project I consider it crucial to get a non-shallow view of how this works and so I began to explore. While there is some limited documentation it is, as so often, not up to date so mostly I worked in the codebases. Yes, plural, because this product spans multiple r...

Notes on Testing Notes

Ben Dowen pinged me and others on Twitter last week , asking for "a nice concise resource to link to for a blog post - about taking good Testing notes." I didn't have one so I thought I'd write a few words on how I'm doing it at the moment for my work at Ada Health, alongside Ben. You may have read previously that I use a script to upload Markdown-based text files to Confluence . Here's the template that I start from: # Date + Title # Mission # Summary WIP! # Notes Then I fill out what I plan to do. The Mission can be as high or low level as I want it to be. Sometimes, if deeper context might be valuable I'll add a Background subsection to it. I don't fill in the Summary section until the end. It's a high-level overview of what I did, what I found, risks identified, value provided, and so on. Between the Mission and Summary I hope that a reader can see what I initially intended and what actually...

Around the Testing World in 28 Ways

The Association for Software Testing has been crowdsourcing a book, Navigating the World as a Context-Driven Tester , for the last three years. Over that time 28 questions or statements about testing have been posed to our community and the various answers collected and collapsed into a single reply. Lee Hawkins, the coordinator of the project, has just blogged about the experience in The wisdom of the crowd has created an awesome resource for context-driven testers . He pulled some statistics out of the records he's kept showing the level of interest in each question or statement, measured by the number of responses from the community. That's the red bars on the chart at the top, ranging in value from 4 to 28. I replied every single time Lee posted, with a very specific mission in mind: I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good fa...

Hiccupps

Search This Blog