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

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