Skip to main content

AST Lean Coffee

 

My second Lean Coffee in a week, this one online with the Association for Software Testing. Here's a few aggregated notes from the conversation.

Why do people want to speak at conferences, and can we support them to get what they need in other ways?

  • Lots of noise recently on Twitter about people being rejected, and discussion of tactics for getting in.
  • So why do people want to speak at conferences?
  • Increase their brand.
  • Be more employable.
  • Be better known.
  • Go to the conference for free.
  • Company will only pay if they are speaking.
  • Share what I've learned.
  • Share my story.
  • Challenge yourself.
  • Because they see others doing it
  • Personal access to "big names."
  • Conferences always have the same speakers.
  • Do people need better access to conferences?
  • Can be a vicious cycle: accepted because we know you; we know you because you speak.
  • Perhaps the return to in-person conferences has increased the demand for speaking slots.
  • People don't know how to sell their talk to conferences
  • Lots of people stick the same proposal into multiple conferences, not tailored
  • I get inspiration from conferences: testing is a lot bigger than I remember day-to-day.
  • If you want to get known, other platforms might not be so good.
  • Conference talks are often amplified widely on social media.
  • What else can we do to boost signal?
  • Magazines, Podcasts, Blogs, Twitter, LinkedIn, Peer Conference, YouTube, ...

What one thing would you prefer never to have to do again (as a tester)

  • Repeatedly explaining something to someone who is lazy or doesn't want to open their mind.
  • Justifying why it's useful having a tester on a team or doing testing.
  • ... One of the best things is explaining to people who want to learn (teaching vs justifying).
  • ... Many different people in project teams think they can tell testers how to work.
  • ... I'm happy to question my own practices for improvemen.
  • ... Providing good feedback and constructive criticism is positive
  • Explaining why you can't automate all the testing.
  • ... Software development has an undercurrent that is trying to destroy good work by testers.
  • Being in a conference where some smartass explains why everyone can be as successful as them.
  • Sitting with a developer while they fix a bug I reported (because they feel they need that reassurance).
  • ... or working with developers that think testing is someone else's job.

Working conditions for testers

  • Inspired by a Twitter thread.
  • The reputation of the gaming industry is dire.
  • Why are big-name companies apparently abusing game testers?
  • What is the culture like?
  • How can we change it?
  • What other industries are bad?
  • Outsourcing companies have been known to abuse juniors particularly.
  • I have worked with people who tell all sorts of tales about game testing.
  • ... a culture of short-term contracts.
  • ... a funding model that means they need to be able to drop people after product release.
  • Tech has a weird relationship to unions.
  • Reasonable pay in tech makes people think we don't need unions.
  • Geography is important, e.g. China and India have a reputation for poor worker conditions.
  • ... e.g. 40 hour week contract but employers expect 996 work.
  • Is it worse for testers than other software professionals?
  • But some people have no choice.

Tactics for learning while testing

  • You have work to do and it has a deadline
  • But you also want to learn new tools, new approaches, new things about your domain
  • Be prepared to gamble some specific time on trying things.
  • ... but abandon it if it's not working out in the time.
  • ... and come back to it on another occasion.
  • Give yourself permission to learn
  • Developers give themselves time and spike tickets.
  • People with seniority need to get better at giving time to their staff.
  • Senior testers tend to be better at making time for learning.
  • Discipline is needed.
  • I only do it when the situation forces it because of time pressure.
  • Look for an opportunity to do something new.
  • You need to practice a thing to get deep with it.
  • Perhaps analyse tasks before jumping into them, for learning opportunities.
  • Ask "can I try this experiment in a different way?"
  • We have a Community Day at work.
  • If you don't have that, then use stealth approaches!
  • Unionise!

Image: https://flic.kr/p/63wFf7


Comments

Popular posts from this blog

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

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

The Best Laid Test Plans

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-- "What's the best format for a test plan?" I'll side-step the conversation about what a test plan is and just say that the format you should use is one th...

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