Sota so Good

Much of Definition of The Engineering Method by Billy Vaughn Koen chimes with what I've come to believe about testing.

In part, I think, this is because thinkers who have influenced my thinking were themselves influenced by Koen's thoughts. In part, also, it's because some of my self-learned experience of testing is prefigured in the article. In part, finally, it's because I'm reading it through biased lenses, wanting to find positive analogy to something I care about.

I recognise that this last one is dangerous. As Richard Feynman said in Surely You're Joking, Mr. Feynman!: "I could find a way of making up an analog with any subject ... I don’t consider such analogs meaningful.”

This is a short series of posts which will take an aspect of Definition of The Engineering Method that I found interesting and explore why, taking care not to over-analogise.

--00--

The leaping off point for Definition of the Engineering Method is the scientific method. From Wikipedia:

The scientific method is an empirical method of acquiring knowledge that has characterized the development of science since at least the 17th century. It involves careful observation, applying rigorous skepticism about what is observed, given that cognitive assumptions can distort how one interprets the observation. It involves formulating hypotheses, via induction, based on such observations; experimental and measurement-based testing of deductions drawn from the hypotheses; and refinement (or elimination) of the hypotheses based on the experimental findings.

Specifically Koen observes that, while the scientific method has been much studied, he does not believe that engineering is simply "applied science" and there is little literature on what he calls the engineering method. Yet engineering has been, is, and will continue to be critical to the way our world is shaped and the way we live in it. Shouldn't we care about how we engineer our environment and ourselves?

(Answer: yes.)

As Koen develops his ideas on what the engineering method could be, he co-opts a term, state of the art (abbreviated as sota), which he takes to be the set of heuristics known by an individual or a group at a specific time. For any pair of engineers, it is likely that their sotas will intersect at some foundational points and then differ where their experience has caused them to specialise on tasks. A given engineer's sota will change through her career, as she finds some heuristics more or less valuable.

This concept is interesting because it allows him to visualise, with simple set diagrams, how problems fall into or outside of the sotas of individuals and groups. This feels neat and I found it easy to nod along to until I read this (p. 31):

The [sota] of the engineering profession defines the best possible engineering solution. This overall solution represents best engineering practice and is the most reasonable practical standard against which to judge the individual engineer. It us a relative standard instead of an absolute one, and like all sotas it changes in time

As a card-carrying context-driven tester, I flinched. Best practice? Really?

Fortunately, in Koen's context, "best" has a specific interpretation (p. 12):

A fundamental characteristic of an engineering solution is that it is the best available from the point of view of a specific engineer. If this engineer knew the absolute good, he would do that good. Failing that, he calculates his best based on his subjective estimate of an informed society's perception of the good.

Sotas allow Koen to represent an engineering sota distinct from a society's sota, and speculate on how this difference can lead to solutions to the wrong problem, or the wrong problem being put forward to be solved. Where sota intersection is smaller, there is likely to be less shared understanding and more chance of problem and solution being incompatible in some important way.

In this consideration of the relationships between the expert and the public, there are echoes of Harry Collins' work on Science Studies. Take this passage (p. 39):

Some argue that we are witnessing a shrinking of [joint efforts between the general population and engineers] as society disciplines the engineering profession because of disagreement over past solutions. No longer is it sufficient for an engineer to assert that a mass transportation system or nuclear reactor is needed and safe ... What is most urgently needed is research to determine the minimum overlap necessary for a non engineer to be technologically literate.

I was also struck by similarities between sotas and the thoughts on the propagation of theory (a term we were using more broadly than its conventional meaning) around communities that Sneha Bhat and I presented in Transforming Theory and Practice:

... we perceive two broad types of theory: behavioural (what the system does) and practical (how to exercise the system). In a typical project the first of these is likely to get reported back to the team in general, but the latter is likely to remain local with either this tester or her peers when they share information that helps them to do their job.

This flow of theory aligns well with the idea that the sotas of different individuals and different can be populated differently, and perhaps even helps to explain how that can be the case for members of the same team with different areas of expertise.

An angle we explored, but I don't think Koen does, is the idea that practitioner knowledge may be tacit, again per Harry Collins. In Transforming Theory and Practice we wrote:

An expert practitioner may add enormous value to a project by virtue of being able to divine the causes of problems, find workarounds for them, and gauge the potential impacts on important scenarios. But they may find it hard to explain how they arrived at their conclusions ... This kind of tacit knowledge is learned over time, and with experience ...

Could tacit knowledge be part of an individual's sota? Is it the case that all engineering decisions are thought to be justifiable in terms of some aspect of a sota? Could the "art" aspect of sota permit undefined intuition? I like these kinds of questions.

But how are sotas relevant to testing? It's relevant to me in my testing because, as part of an engineering team solving problems for people who are generally not engineers, I want to do these kinds of things:

recognise that the customer perspective is not the team's perspective
recognise that my personal perspective is not the same as my colleagues' perspective
look for the aspects of all relevant perspectives that are most relevant to the problem
look for ways to communicate with all parties such that the right information is available to make informed choices about aspects of the problem that matter

The sota, and Koen's Venn-style diagrams, give me some language for, and visualisation of, that space.

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

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

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

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

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

ChatGPTesters

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-- "Why don’t we replace the testers with AI?" We have a good relationship so I feel safe telling you that my instinctive reaction, as a member of the Tester's Union, is to ask why we don&

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

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

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

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

Hiccupps

Search This Blog