Skip to main content

What Do I Know?

My kids begged to go to the Funky Fun House this half-term. I've got nothing against these soft play barns particularly - I've been to stacks of them - but, for me, there's generally little that's funky about echoing industrial spaces crammed with primary-coloured foam, covered in crumbs and reeking of decades worth of half-eaten fish and chips.

To be fair, though, this one is in a (ware)house and the girls do have a lot of fun. In fact, I used to have fun too when they wanted me to play on the thing with them. These days they just see me as the shoe and coat monitor and provider of snacks. (Oh, and somone to take the mickey out of in front of their friends.)

And that's how it went down this time too, except that I was engrossed in a book called Are We All Scientific Experts Now? by Harry Collins. A book I read in its entirety at my sticky table, that blocked out the noise of the toddlers in the padded prison enclosure that I'd ended up sitting next to; that insulated me from the random draughts of hyper-accelerated cold, cold air that was injected from somewhere behind me into the sweaty fug whenever some sensor thought it necessary, and whose trajectory I seemed to be on; and that even made me smile benevolently as I chucked back the plastic balls to whichever tiny terror had lobbed them at me from an unexpected direction.

This is a great book.

Collins describes three "waves" of our understanding of how science operates coming out of a discipline called Science Studies. At a simple level, in the first wave scientists were perceived to be engaged in tests of nature and able to pronounce on the facts and foibles of it, uncontested. The white coat was enough to convince the public that good work was being done in a trustworthy, honourable and correct manner.

In the second wave, it was realised that the story is more complex and that experimenting on nature can have an effect on nature. The subject of the experiment is not constant or consistent, and the experimenters are part of its context not removed from it. They are human and can have bias and opinion and motivations outside of the "first wave" view of science. Scientific scandals emerged and the public began to lose faith in scientists. The third wave, ongoing now, is to find a way to "treat science as special without telling fairy stories about it".

The book provides an exploration of what it means to be an expert, and a rejection of the idea that Collins terms default expertise: that these days, in our society, anyone can be considered an expert in pretty much anything. It includes a taxonomy of expertise that seeks to provide a basis on which to explain the difference between those people who can talk lucidly, broadly, deeply - seemingly expertly - about a subject and those people who are on the inside of the subject, in the milieu of it, actively engaged in the community of it, with access to its unwritten contexts, its tacit knowledge.

He terms these two classes ubiquitous expertise and specialist expertise and notes that it can be hard for outsiders to tell the difference between them. And he has a lovely turn of phrase for the way that, to those outsiders, complexities around an issue can be elided, doubt can be replaced by certainty and rough edges magically smoothed away: "distance lends enchantment".

The conclusion of the book is that we all have a level of (ubiquitous) expertise in some areas with which we are implicitly engaged through our daily lives - we can all speak our native language or drive a car - and we all have some measure of (specialist) expertise in some areas that we choose - such as our day jobs. But these kinds of expertise do not generally equip us, of themselves, to be scientific experts. We can become scientific experts, but it takes a lot of hard work; there is no substitute for effort and engagement with the scientific community.

We do not even necessarily possess the skills to distinguish between competing (apparent) scientific experts with any reliability. And if we think that we do,  if we accept the views of others with similar lack of scientific expertise as if it was backed by scientific expertise, then society will be the worse for it because, despite being staffed by humans, and thus flawed in the ways that humans are flawed, the ethos and methodology of science should be lauded and respected.
Image: Amazon

Edit: I wrote about a related lecture in Quality is Value-Value to Somebody.

Edit: I'm grateful to my colleague Ros Shufflebotham who alerted me to the fact that "distance lends enchantment" is due to Thomas Campbell.

Comments

Popular posts from this blog

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 in your working context and the way

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 answer would be almost meaningless and certa

Not Strictly for the Birds

  One of my chores takes me outside early in the morning and, if I time it right, I get to hear a charming chorus of birdsong from the trees in the gardens down our road, a relaxing layered soundscape of tuneful calls, chatter, and chirrupping. Interestingly, although I can tell from the number and variety of trills that there must be a large number of birds around, they are tricky to spot. I have found that by staring loosely at something, such as the silhouette of a tree's crown against the slowly brightening sky, I see more birds out of the corner of my eye than if I scan to look for them. The reason seems to be that my peripheral vision picks up movement against the wider background that direct inspection can miss. An optometrist I am not, but I do find myself staring at data a great deal, seeking relationships, patterns, or gaps. I idly wondered whether, if I filled my visual field with data, I might be able to exploit my peripheral vision in that quest. I have a wide monito

Testing (AI) is Testing

Last November I gave a talk, Random Exploration of a Chatbot API , at the BCS Testing, Diversity, AI Conference .  It was a nice surprise afterwards to be offered a book from their catalogue and I chose Artificial Intelligence and Software Testing by Rex Black, James Davenport, Joanna Olszewska, Jeremias Rößler, Adam Leon Smith, and Jonathon Wright.  This week, on a couple of train journeys around East Anglia, I read it and made sketchnotes. As someone not deeply into this field, but who has been experimenting with AI as a testing tool at work, I found the landscape view provided by the book interesting, particularly the lists: of challenges in testing AI, of approaches to testing AI, and of quality aspects to consider when evaluating AI.  Despite the hype around the area right now there's much that any competent tester will be familiar with, and skills that translate directly. Where there's likely to be novelty is in the technology, and the technical domain, and the effect of

Postman Curlections

My team has been building a new service over the last few months. Until recently all the data it needs has been ingested at startup and our focus has been on the logic that processes the data, architecture, and infrastructure. This week we introduced a couple of new endpoints that enable the creation (through an HTTP POST) and update (PUT) of the fundamental data type (we call it a definition ) that the service operates on. I picked up the task of smoke testing the first implementations. I started out by asking the system under test to show me what it can do by using Postman to submit requests and inspecting the results. It was the kinds of things you'd imagine, including: submit some definitions (of various structure, size, intent, name, identifiers, etc) resubmit the same definitions (identical, sharing keys, with variations, etc) retrieve the submitted definitions (using whatever endpoints exist to show some view of them) compare definitions I submitted fro

Testers are Gate-Crashers

  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-- "Testers are the gatekeepers of quality" Instinctively I don't like the sound of that, but I wonder what you mean by it. Perhaps one or more of these? Testers set the quality sta

Vanilla Flavour Testing

I have been pairing with a new developer colleague recently. In our last session he asked me "is this normal testing?" saying that he'd never seen anything like it anywhere else that he'd worked. We finished the task we were on and then chatted about his question for a few minutes. This is a short summary of what I said. I would describe myself as context-driven . I don't take the same approach to testing every time, except in a meta way. I try to understand the important questions, who they are important to, and what the constraints on the work are. With that knowledge I look for productive, pragmatic, ways to explore whatever we're looking at to uncover valuable information or find a way to move on. I write test notes as I work in a format that I have found to be useful to me, colleagues, and stakeholders. For me, the notes should clearly state the mission and give a tl;dr summary of the findings and I like them to be public while I'm working not just w

Build Quality

  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-- "When the build is green, the product is of sufficient quality to release" An interesting take, and one I wouldn't agree with in general. That surprises you? Well, ho

Make, Fix, and Test

A few weeks ago, in A Good Tester is All Over the Place , Joep Schuurkes described a model of testing work based on three axes: do testing yourself or support testing by others be embedded in a team or be part of a separate team do your job or improve the system It resonated with me and the other testers I shared it with at work, and it resurfaced in my mind while I was reflecting on some of the tasks I've picked up recently and what they have involved, at least in the way I've chosen to address them. Here's three examples: Documentation Generation We have an internal tool that generates documentation in Confluence by extracting and combining images and text from a handful of sources. Although useful, it ran very slowly or not at all so one of the developers performed major surgery on it. Up to that point, I had never taken much interest in the tool and I could have safely ignored this piece of work too because it would have been tested by

The Best Laid Test Plans

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-- "What's the best format for a test plan?" I'll side-step the conversation about what a test plan is and just say that the format you should use is one that works for you, your coll