Island Records

I was invited onto the Testers' Island Discs podcast recently. Testers' Island Discs is

... a podcast focused around software testing and storytelling hosted by Mark Winteringham.

The concept is straightforward: each episode, Mark interviews a different member of the global software testing community to talk about their career, interspersed with clips and discussions of the music that they love. Every guest gets to select five songs and one book to take with them to the island.

Music was my life for a long, long time. I was in bands, I did my own solo music, I wrote a fanzine and occasionally for "proper" publications too, I attended gigs several nights a week, and I DJed on student and community radio stations. I built up a big record collection stacked around the house and in the loft but when my daughters got old enough to need their own bedrooms I had to sell it to make space.

Although I never counted, I estimated that there were around 12-15000 albums, singles, flexidiscs, and CDs driven away in the bloke from Cambridge market's long wheelbase Ford Transit that sad, sad day.

Getting down to five tunes was tough. I originally thought I might choose from records whose sleeves I've used at the top of posts here on Hiccupps but, in the end, I settled for a handful that gave and continue to give me an emotional reaction. I hope you enjoy them.

Run DMC, Sucker M.C.'s (Profile) from Run DMC LP

Run DMC were the first band I got deeply into. It's a long time ago now, 1986 when their Raising Hell album came out, when I heard them on, I think, Janice Long's evening show on Radio 1. Hard, basic beats, chunky scratching, and rock guitar topped off with tag-team rapping.

I went up to Birmingham the next weekend and bought it then went back in later weeks to get the first album, Run DMC, and the second, King of Rock. All three are classics. Playing anything from these takes me back to that time when music had just got electrifying for me.

Cable, Oubliette (Infectious) from Down-lift the Up-trodden 10"

By the mid 1990s I'd become a bit bored by indie guitar bands but Cable (and also Compulsion with tracks like Why Do We Care?) reignited the excitement for me when they pinned me to the back wall of a tiny venue in Reading. I hoovered up their back catalogue on Krunch! and everything they put out afterwards.

I interviewed them at Nottingham Rock City and heard som outrageous stories about being kicked out of Oasis's studio at gunpoint! An oubliette is a kind of dungeon that you can only access through a trapdoor in its ceiling, by the way.

Jerry Reed, Thank You Girl (RCA) from When You're Hot You're Hot LP

For my sins, I have a soft spot for that extremely 1970s film, Smokey and the Bandit. Burt Reynolds stars as The Bandit while his truck-driving sidekick, The Snowman, is played by the musician Jerry Reed. Reed also sings on the theme song for the film, East Bound and Down. It's great song and I used to sing it to my daughters to help get them off to sleep when they were babies.

I bought the soundtrack album on vinyl but when it arrived the sleeve was in awful condition. The place I ordered it from offered to let me choose something else as compensation and I picked a Jerry Reed album, When You're Hot You're Hot. Thank You Girl spoke to me immediately: "I wanna thank you girl/For loving me/I wanna thank you girl/For all the happiness you brought to me".

If it sounds cheesy to say it out loud, in the song it's simply magical. When me and my wife got married we chose this, Slade's Coz I Luv You, and I Walk The Line by Johnny Cash to play while we signed the register.

Pram, Cumulus (Too Pure) from Iron Lung EP 12"

The last term of my Master's degree was for project work, to write a dissertation. Naturally I spent a large part of it on a future-retro, techno-fear, short black and white film recorded on a silent Super-8 camera with a couple of my mates from the course. The film was called Wireless and it's about how phono terrorists are trying to break the state's stranglehold on the population which they control with mind-numbing music broadcast everywhere all of the time. We got all this old computer equipment out of skips at the Engineering department and borrowed a hall to set them up in from the college I was living in. Editing it was amazing, all these little strips of film hanging up on washing lines around my flat for weeks until we got it spliced together and transferred to video.

That was a major milestone, but we still needed to put a soundtrack on it and because I was a DJ and had a little DJ mixer and VCR that you could use to dub sound onto video tape it fell to me to do it, but the equipment was so primitive I mixed it live with three or four tape decks and a turntable. The sounds effects were all on audio tape, wound back to just the right place that I could put them into a tape deck and play them without needing to cue them up. A large part of the soundtrack was an amazingly atmospheric track, Cumulus, by Pram which I had on a red vinyl 12" single called Iron Lung.

Years later, for reasons I don't recall, me and my daughters used to play a weird version of follow-the-leader to the same track, leaping around the living room and trying to pull the strangest poses we could. So when I hear this track I have two wonderful memories.

The Guy Who Invented Fire, Glow (Intellectos) from I Didn't Get Where I Am Today EP

No YouTube for this one, but I've made an MP3 available.

I used to make music in bands, in an Anglo-French duo, and alone as The Guy Who Invented Fire. I used an Amiga computer and tracker freeware based on Ultimate Soundtracker which was a four-channel software sequencer that played 8-bit samples.

This track is one of mine, probably the one I'm most proud of, in part because it was the point at which I realised I didn't need to be able to play anything more than once to be able to use it. I could simply record myself tinkering and then curate the best bits from it. I didn't consider it this way at the time, but it's really a step back from work to meta-work.

It was released on an EP called I Didn't Get Where I Am Today by a U.S. label, Intellectos. The title is from The Fall and Rise of Reginald Perrin, fact fans.

I've published a list of links to stuff I talked about on the podcast at Testers' Island Links.

Images: Pinterest/ebid, Discogs

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