I Done the Ton

This is the 100th post on Hiccupps.

I started the blog just under two years ago with the self-challenge of writing 50 posts in a year and a manifesto of sorts:

to blog primarily about testing and related areas
to explore and document my thinking
to try to offer something different from other blogs
to be truthful
to write well
to be myself ...
... but not come across as (too much of) a pretentious or pompous pillock
to protect the confidentiality of my company, customers and colleagues, where mentioned
to have the freedom to write anything I want to, within the other constraints

I was inspired most directly by Abakas and QA Hates You which were both being updated frequently, spoke with a distinctive voice and were provocative in their own separate ways. Catherine Powell would frequently cover topics away from testing, with an eye to making a point relevant to it and always clearly from a practitioner's perspective. Brian Noggle's persona was - and is - more aggressive and humourous, frequently using examples of failure to make his points but again with practical experience backing him up.

I'd been a tester - and test manager - for a handful of years by then. As usual in start-ups, I'd done all sorts of stuff prior to that, including software development, web sites, marketing, pre-sales, training, IT, technical support and tea boy. When we started the company part of my work was in Java development because we decided to implement a rich UI in that language. So I learned Java on the job (with no commercial programming experience, Prolog was my "best" language at that point) and then discovered how I like to to (try to) manage people, projects, infrastructure and the rest by building up the Dev team over the following years.

As time went by the company grew, the codebase grew, the product grew, our customer base grew and our bug database got gruesome. It became clear that we needed to do something less ad hoc in testing and we recruited a Dev manager while I started a test team from scratch.

Researching background material, the first book I bought was Lessons Learned in Software Testing. Wow. So many of my intuitions about how I felt I wanted to test were being described and many pits I might otherwise have fallen into were being signposted. We have a couple of copies of the book in our company library and I recommend it to all new members of the test team and developers who ask. I still dip into it and, when I do, frequently find some nugget of information that's relevant to what I'm doing right there and then.

As I got more experienced I started to think more deeply about what I was doing and how I was doing it and tried to tease out where my actions, intuitions, ideas and mistakes were coming from. Then I wondered whether there might be value in sharing those thoughts. Personally, I wanted to make them coherent enough that I could express them reliably. For others, I hoped to provide a resource; not Thomas' Golden Laws of Testing, but one man's take on stuff that has mattered to, bears on or came out of his time spent testing software.

I'd like to think I've achieved what I set out to. I managed 50 posts in that first year and the centennial's arriving just before the second anniversary. Reading back over earlier posts I'd probably change a few things if I was going to start them now but by and large I'm happy they stick to the manifesto. Colleagues recognise me in the writing and noting now how often it seems that I've mentioned cups of tea, referenced musicians and wedged in an excruciating phonetic gag, I recognise myself too.

Trying to post around once a week has been a useful discipline. If nothing else it's motivational. I've managed to carve out time even when life and work have been hectic and I've improved my productivity both in writing the posts and in the writing I need to do day-to-day.

It should be no surprise that trying to get a thought out in a form someone else can understand forces you to clarify your own understanding, but it's perpetually interesting to me how much the idea I'm trying to express can have its resolution increased - not to mention its core components adjusted - trying to blog about it. Paul Heaton of the Housemartins put it brilliantly, for the parallel case of song writing:

"And then it's like doing a really difficult crossword. The thing is to get the first clue – that's when you realise what this song is going to become. It's going to be something good, because you realise for the first time that, for the whole of your life, you've held opinions about this subject. And that's a really enjoyable part of the job."

I've found that I learned a lot from just researching statements or implicit assumptions that I've made in the first draft of a post. I'm also not too proud to say that I've learned a lot about testing from my colleagues. Developers and testers coming from other companies, with longer experience than me in and around testing, have given me approaches, heuristics, resources, technology, ideas and more that I've absorbed into my own work and attitude.

I've uncovered (to myself) that I'm very interested in value, efficiency (particularly of communication and collaboration), sharing, thinking before acting, idea generation, maximising my own skills, trying to show that testers are not islands and more. I already knew that I loved wordplay, and tea.

I'm really enjoying the act of writing, and of finding images that suit the post, with some often tangential reference which I hope readers might notice in their peripheral vision. In fact, trying to inject these has given some insight into how to spot them, and by extension is a good exercise in looking for unexpected connections, unintended consequences, unwanted associations and so on in the day job.

It looks like others might be seeing some of the value I'd hoped for too: the readership is increasing (according to Blogger's numbers) and I've had interesting discussions with other testers on the back of the blog, I'm approaching 300 followers on Twitter (still can't believe that many people care, even at the low-level approximation to caring that following implies) and I've been asked to contribute to the Testing Planet, which I've done a couple of times so far.

There's a sidebar on the full version of this page that shows the current most popular posts as judged by readers, but here's some I found I was particularly happy with when reading them back this week:

Drawing Conclusions: because analogy can be a powerful tool and because it illustrates (for me, anyway) how testing is part of life, which people often seem to forget
Dev Ice Manager: because of the audacious title and because it's transcribed almost verbatim
Test Automation is not Automated Testing: because of the material it covers and the testers who collaborated on it
Setting the Quality: because the idea likely wouldn't have come to me if I hadn't been blogging
Ask a Stupid Equestrian: because it's an attempt to engage non-testers and feedback from workmates suggests that it worked

And so what next? Well, why stop when I'm having pun?
Image: http://flic.kr/p/6f6sXg

Comments

Phil said…

Congrats on making 100, looking forward to 100 more

Sounds like you've got a lot out of blogging, so have I, more people should do it

September 9, 2013 at 9:55 PM

Ajoy Singha said…

Congratulations for 100th post. What about getting the 101th published in Testing Circus magazine?

September 10, 2013 at 5:25 PM

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

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

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

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

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

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

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

Hiccupps

Search This Blog