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

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

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

Am I Wrong?

I happened across Exploratory Testing: Why Is It Not Ideal for Agile Projects? by Vitaly Prus this week and I was triggered. But why? I took a few minutes to think that through. Partly, I guess, I feel directly challenged. I work on an agile project (by the definition in the article) and I would say that I use exclusively exploratory testing. Naturally, I like to think I'm doing a good job. Am I wrong? After calming down, and re-reading the article a couple of times, I don't think so. 😸 From the start, even the title makes me tense. The ideal solution is a perfect solution, the best solution. My context-driven instincts are reluctant to accept the premise, and I wonder what the author thinks is an ideal solution for an agile project, or any project. I notice also that I slid so easily from "an approach is not ideal" into "I am not doing a good job" and, in retrospect, that makes me smile. It doesn't do any harm to be reminded that your cognitive bias

Play to Play

I'm reading Rick Rubin's The Creative Act: A Way of Being . It's spiritual without being religious, simultaneously vague and specific, and unerring positive about the power and ubiquity of creativity.  We artists — and we are all artists he says — can boost our creativity by being open and welcoming to knowledge and experiences and layering them with past knowledge and experiences to create new knowledge and experiences.  If that sounds a little New Age to you, well it does to me too, yet also fits with how I think about how I work. This is in part due to that vagueness, in part due to the human tendency to pattern-match, and in part because it's true. I'm only about a quarter of the way through the book but already I am making connections to things that I think and that I have thought in the past. For example, in some ways it resembles essay-format Oblique Strategy cards and I wrote about the potential value of them to testers 12 years ago. This week I found the f

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

Test Now

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 is the best time to test?" Twenty posts in , I hope you're not expecting an answer without nuance? You are? Well, I'll do my best. For me, the best time to test is when there

Rage Against the Machinery

  I often review and collaborate on unit tests at work. One of the patterns I see a lot is this: there are a handful of tests, each about a page long the tests share a lot of functionality, copy-pasted the test data is a complex object, created inside the test the test data varies little from test to test. In Kotlin-ish pseudocode, each unit test might look something like this: @Test fun `test input against response for endpoint` () { setupMocks() setupTestContext() ... val input = Object(a, OtherObject(b, c), AnotherObject(d)) ... val response = someHttpCall(endPoint, method, headers, createBodyFromInput(input) ) ... val expected = Object(w, OtherObject(x, y), AnotherObject (z)) val output = Object(process(response.getField()), otherProcess(response.getOtherField()), response.getLastField()) assertEquals(expected, output) } ... While these tests are generally functional, and I rarely have reason to doubt that they

A Qualified Answer

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 ,   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-- "Whenever possible, you should hire testers with testing certifications"  Interesting. Which would you value more? (a) a candidate who was sent on loads of courses approved by some organisation you don't know and ru

README

    This week at work my team attended a Myers Briggs Type Indicator workshop. Beforehand we each completed a questionnaire which assigned us a personality type based on our position on five behavioural preference axes. For what it's worth, this time I was labelled INFJ-A and roughly at the mid-point on every axis.  I am sceptical about the value of such labels . In my less charitable moments, I imagine that the MBTI exercise gives us each a box and, later when work shows up, we try to force the work into the box regardless of any compatiblity in size and shape. On the other hand, I am not sceptical about the value of having conversations with those I work with about how we each like to work or, if you prefer it, what shape our boxes are, how much they flex, and how eager we are to chop problems up so that they fit into our boxes. Wondering how to stretch the workshop's conversational value into something ongoing I decided to write a README for me and