Heuristics for Working: Doing

For a while now I've been collecting fieldstones on the topic of heuristics for working. Some of these are things that I've said to others, some of them are things that I've thought about when considering some aspect of myself or how I work, and others have come from books I've read, talks I've attended, and workshops I've participated in.

I've made a handful of rough categorisations and I'll put each set in a post under the tag Heuristics for Working.

But what do even I mean by heuristics for working? Good question. I mean rules of thumb for situations that arise in the workplace. They are bits of advice that can be useful to consider but don't offer any guarantees and will not always apply.

The collection is surely idiosyncratic, context-sensitive and perhaps too specific and too general in turn. Welcome to my head. I haven't sat down and tried to elaborate or enumerate more, or to try to fill the gaps. Everything here has arisen and been noted in the moment, although a good chunk of it is stuff that I've thought about in the past too.

Of course, having heuristics doesn't mean that I remember to use them, or pick a reasonable one when I do remember, or make a good choice when I have remembered and picked a reasonable one. That's part of the rich tapestry, isn't it? At least externalising them and listing them gives me an opportunity to try to understand and maybe change the way I work, the way I am biased, or the way I want to be.

Along the way, I got to wondering if there's one overriding heuristic, one heuristic to rule them all, a meta heuristic. If there was, I think it might run along these lines:

Question your heuristics.

I hope there's something interesting and perhaps even helpful here for you.

--00--

Remember that sometimes good work leads to bad outcomes.

Remember that sometimes bad work leads to good outcomes.

Wonder how you are doing this piece of work right now.

Don't expect perfection.

Ask what factors are relevant.

Ask how you can best make them obvious to those who need to know them.

When writing: start small, aggregate, edit.

Ask "what is the thing"? (The absolute key point, the heart of the matter, the nub of the problem.)

Can you draw a picture or a table rather than keep talking or writing?

What's the simplest explanation? (What is the thing of this thing?)

What's the simplest model that fits well enough for now?

Where does this thing fit into a universe of things? What dimensions are appropriate to map the universe? Can I draw it?

Give yourself a chance to review something before it goes out.

Deliberately take two bites at the cherry: get first thoughts down right now. Wait. Review and think again.

Organise your work as early as makes sense:

Use meaningful names for your data, files, folders.

"new", "latest", "new_2", "other_way" and so on are not meaningful names.

"windows10_java_18u34_english_firefox_UTF8_JS-disabled", "windows10_java_18u34_english_firefox_UTF8_JS-enabled" are meaningful names in a scheme likely on a path to a nightmare.

When scenarios get complicated use identifiers for your data, files, folders and map a table of variables to them.

You will not remember tomorrow that "new36" is the input that generated "out_latest".

Store related work in related places. Ideally the same place.

Don't store unrelated work in that place.

Be consistent about how you name things.

Be consistent about how you record things.

If you're not inventing process each time you are freer to be doing the work.

Break work down into small chunks and check each chunk.

Ask how you could get evidence that you've done what you wanted to.

Ask what would be true if you had done the right thing.

If you don't know how to check whether what you're about to attempt worked, ask yourself whether doing it now is the right move.

Apply your testing skills to yourself and your work.

When you have an idea, don't rely on yourself to remember it. Externalise it.

Collect notes in the places they'll be useful.

Think big, act small.

Seek the the smallest piece of work that provides a benefit and doesn't actively contradict the overall mission.

Know the mission.

Note when the mission changed.

Change the mission consciously.

Seek the same result in a cheaper way (for some relevant measure of cost).

Seek better results at the same cost (for some relevant measure of goodness).

Find a way to iterate quickly.

Plan. Do. Check. Act.

Ask whether you can script it if it's regular and repeated.

Ask whether semi-automation is enough of a win at sufficiently small cost.

Find an an analogy to your problem and look for a solution in that space.

Search for a tool or someone else's solution.

Ask where you're trying to get to.

Ask whether there a direct route from here to there? Also, any other routes.

Can you work backwards from there and forwards from here?

Challenge yourself.

Gain credibility by doing credible things.

Gain credibility by doing things credibly.

Gain credibility by talking from experience.

From time to time put yourself outside your comfort zone. Watch how you react.

Wonder how you could react differently next time.

Work to make sure there is a next time.

Image: 45cat

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

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

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

Notes on Testing Notes

Ben Dowen pinged me and others on Twitter last week , asking for "a nice concise resource to link to for a blog post - about taking good Testing notes." I didn't have one so I thought I'd write a few words on how I'm doing it at the moment for my work at Ada Health, alongside Ben. You may have read previously that I use a script to upload Markdown-based text files to Confluence . Here's the template that I start from: # Date + Title # Mission # Summary WIP! # Notes Then I fill out what I plan to do. The Mission can be as high or low level as I want it to be. Sometimes, if deeper context might be valuable I'll add a Background subsection to it. I don't fill in the Summary section until the end. It's a high-level overview of what I did, what I found, risks identified, value provided, and so on. Between the Mission and Summary I hope that a reader can see what I initially intended and what actually...

On Herding Cats

Last night I was at the Cambridge Tester meetup for a workshop on leadership. It was a two-parter with Drew Pontikis facilitating conversation about workplace scenarios followed by an AMA with a group of experienced managers. I can't come to work this week, my cat died. Drew opened by asking us what our first thoughts would be as managers on seeing that sentence. Naturally, sadness and sympathy, followed by a week ? for a cat ? and I only got a day for my gran! Then practicalities such as maybe there's company policy that covers that , and then the acknowledgement that it's contextual: perhaps this was a long-time emotional support animal . Having established that management decisions are a mixture of emotion, logic, and contingency Drew noted that most of us don't get training in management or leadership then split us into small groups and confronted us with three situations to talk through: Setting personal development goals for others. Dropping a clange...

Reasonable Doubt

In Your job is to deliver code you have proven to work Simon Willison writes: As software engineers we ... need to deliver code that works — and we need to include proof that it works as well. He is coming at this from the perspective of LLM-assisted coding, but most of what he says applies in general. I think this is a reasonable consise summary of his requirements for developers: Manual happy paths: get the system into an initial state, exercise the code, check that it has the desired effect on the state. Manual edge cases: no advice given, just a note that skill here is a sign of a senior engineer. Automated tests: should demonstrate the change like Manual happy paths but also fail if the change is reverted. He notes that, even though LLM tooling can write automated tests, it's humans who are accountable for the code and it's on us to "include evidence that it works as it should." Coincidentally, just the week before I read his post I told one of my...

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

Why Test, Test What, Then How?

There was a time when testing was all about the mnemonics . Well, we had no AI back then so thinking about our human craft and how to share what we had learned using our human intelligence with other engaged humans for later recall in their human heads seemed important. But this post isn't about dumping on AI. It isn't about mnemonics either even if WTTWTH does look like something that'd fit well into that ancient world. No, this post is just a snappier version of what I said to my team this week when I was walking through some testing I'd done the day before. It was concerned with a change to a particular turn in the dialog system we're building where multiple variables are in play, some populated by an external call to an LLM service. I wanted to make the point that the bulk of the testing work was done in the research I did and the spreadsheet I made, not in the interaction with our product. That spreadsheet was the result of me looking in our service's cod...

Open Your Mind

Jerome Groopman, in How Doctors Think , reviews ways in which doctors can make poor choices, identifies potential causes, and suggests some practices, for both doctor and patient, that can help to prevent them. I find this interesting for a couple of reasons: first, I work in the health space, although not in a therapeutic area and, second, I like to reflect on my own thought processes. I'll take three broad themes from Groopman's analysis: the business of healthcare and how that impacts a physician's ability to practice; the doctor-patient relationship and how that impacts the experience of both sides; and the cognitive failings that impact a correct and timely diagnosis for any given patient. Naturally, these overlap. The book is written from the perspective of the notoriously commercialised American medical system and is around 20 years old, so doubtless some of the details are different outside of the US and have changed since pu...

Better Isolate Than Never

How do you test a product with distributed logic and non-deterministic components? Well, it depends on the product and when the question is asked. This post is one answer, for now. A service I work on exposes an API for internal and external clients and calls multiple other services. It orchestrates a reasonably complex journey for a user, with their inputs and the responses of the services determining each step. Our customers can configure the service to provide a variant of the standard journey for their users. This gives them choices on the available steps, the order of the steps, and, importantly, some of the logic for taking particular steps. This configuration lives in a different repository to the service, not owned by us, and it can be changed and deployed independently from the service. As you can imagine, we test our service in multiple ways at different granularities using the usual tooling, including unit tests fo...

Hiccupps

Search This Blog