Skip to main content

A Model Prank

Yesterday I was listening to an episode of Arts and Ideas hosted by Matthew Sweet. The topic was pranks and the first request he made of his guests was for a typology of the terms prank, hoax, stunt, and practical joke. No one was prepared to give one but, through the course of the programme, they clearly preferred one term over the others in specific instances or tried to bypass the distinctions by claiming that what mattered was whether there was a laugh.

This is no great surprise. Categories invariably have fuzzy boundaries although, famously, we like to think that we can know where something belongs "when we see it." My thoughts turned to work, and the problem of stakeholders using sets of overlapping terms when discussing what they want with no time for conversations about the meanings ("don't give me all that semantics!").

So I thought, on 1st April, I would take the fool's errand of trying to imagine working on a project where those concepts were important and I wanted to try to understand the space. Here's what I came up with in a short first pass, deliberately not looking for any oracles.

Potentially relevant factors:

  • Perpetrator: the person(s) or institution that carried out the act
  • Intended outcome: what the perpetrator wanted to achieve, e.g. to generate humour, to get revenge, to commit a crime.
  • Intended victim: who or what the perpetrator wanted to commit the act against e.g. a person, group, or institution.
  • Intended audience: who the perpetrator thinks will witness the act, or its consequences.
  • Intended extent: how deeply affected the perpetrator wants the victim to be.
  • Legality: whether the act is lawful in the place where it occurred.
  • Morality: whether the act is morally acceptable either in its content or execution for any party involved.
  • Context of the act: whether the act takes place somewhere that the victim can reasonably expect to involve some deliberate bending of the truth (e.g. a docudrama or a magic show) or not (e.g. with a trusted friend, on the BBC news.)
  • Grooming: the extent to which the perpetrator has set the victim up for the act.
  • Relationship: the way that the victim views their relationship to the perpetrator.
  • Deceit: whether the act is designed to mislead the victim.
  • Reaction of the victim: whether or not the victim is mislead by the act.
  • Intent to reveal: whether the perpetrator intended for the victim to know about any deception.
  • Length of time before reveal: how long the victim is left not knowing that there was a trick of some kind.

Other thoughts:

  • intention vs actuality. Several of my categories are about the perpetrator's intent, but things might turn out differently and so have an unintended consequence and so change the nature of the act.
  • practical joke, prank, and hoax have some sense of violated expectation but a prank or a joke need not have deceit.
  • an act might start as one thing and then get out of hand and become another.
  • the show's participants talk about both jokes and practical jokes. Could a practical joke ever not be a joke?
  • is a hoax still a hoax if it does not succeed in deceiving?
  • On what axes does me telling a friend that the moon is made of cheese differ from a national newspaper splashing that story.
  • How do the internet and social media play in this space?
  • How to differentiate the terms in question from a lie, a white lie, perjury, a con, a fraud, a magic trick, an advert, a dramatisation of real events, a factual inaccuracy in a respected journal due to human error, outdated material which was true when it was written but is true no longer, publicity-generating acts, telling kids that Father Christmas exists, a tall tale, propaganda, conspiracy theories, sending someone on a fool's errand ...


The image above is from a Miro board I am working on for a current project where I'm going through exactly this kind of process. 

In it, I've made an informal table with factors as columns (the headers are the blue and red tickets just above the horizontal line) and instances (the leftmost green tickets) on the rows. In the context of this blog post an instance might be a scenario where a child places a whoopee cushion on their dad's chair at dinner time or where an artist sprays paint on a wall to make a point about green spaces in urban areas.

Around the table (yellow tickets and images) are additional thoughts and evidence associated with a factor or instance. On the extreme right hand side are unanswered questions and ideas.

I am iterating a model into existence by taking instances and considering them against the factors I have in mind. As I have added more instances, patterns have begun to emerge and factors have been added, removed, merged, or split.

Towards the bottom of the table there are a bunch of rows with no obvious pattern. That suggests a place to start trying to generalise. Could these each be specific examples of a broader family? 

I can also begin to ask questions to fill in gaps. If I have no instance with features X, Y, and Z, the table will show me and I can try to reverse-engineer something that fits. Going in this direction is usually interesting because it forces me against whatever bias or blinkers I instinctively bring to the analysis.

Of course, how long to spend on such a model-building exercise is not always obvious. I tend to want to share it and get some feedback and new suggestions sooner rather than later. So I'll stop here.
Image: Banksy/Instagram (via The Art Newspaper)

Comments

Popular posts from this blog

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...

Can Code, Can't Code, Is Useful

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-- "If testers can’t code, they’re of no use to us" My first reaction is to wonder what you expect from your testers. I am immediately interested ...

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...

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 ...

Express, Listen, and Field

Last weekend I participated in the LLandegfan Exploratory Workshop on Testing (LLEWT) 2024, a peer conference in a small parish hall on Anglesey, north Wales. The topic was communication and I shared my sketchnotes and a mind map from the day a few days ago. This post summarises my experience report.  Express, Listen, and Field Just about the most hands-on, practical, and valuable training I have ever done was on assertiveness with a local Cambridge coach, Laura Dain . In it she introduced Express, Listen, and Field (ELF), distilled from her experience across many years in the women’s movement, business, and academia.  ELF: say your key message clearly and calmly, actively listen to the response, and then focus only on what is relevant to your needs. I blogged a little about it back in 2017 and I've been using it ever since. Assertiveness In a previous role, I was the manager of a test team and organised training for the whole ...

Software Sisyphus

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-- "How can I possibly test 'all the stuff' every iteration?" Whoa! There's a lot to unpack there, so let me break it down a little: who is suggesting that "al...

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...

Why Question?

Questions are a powerful testing tool and, like any tool, can be used in different ways in different scenarios with different motivations and different results. A significant part of my role is generating questions and I will generally have a lot of them. I will rarely ask them all, though, and I've put a lot of time and effort into learning to be comfortable with that. A couple of examples: I was in a meeting this week where the technical conversation was too deep for me to give a perspective from a position of knowledge. I could have disengaged, but I didn't. Instead, I asked occasional questions, not wanting to derail the discussion or disrupt the flow. Some were detail questions, to help grow my understanding. Some were scoping questions, to help understand motivations. The one that really landed, however, was about the focus of the meeting. Although I couldn't contribute at a low level, I understood enough to suspect that we were not discussing the key problem tha...