~/talk

Working With Developers: A Tester's Survival Guide

on YouTube 41m
Talkat TestMu Conference 2026 · 2026-08-19..08-21· [soft-skills]

speaker

name:Wessel Braakman
x:BraakmanWessel

resources

video:https://youtu.be/XwTE2cc6q-A
slides:none on file

summary

Argues that a tester’s success rests on adapting communication to developer personalities and shows concrete before/after scripts: leading with impacts 30% of users flips a decisive developer from dismissive to fixing the bug, giving screenshot/video evidence plus reproducible steps wakes an analyst, and inviting collaboration wins over supporters and enthusiasts; traces a systems-thinker discovery that a validation change affects import and batch jobs; fixes ship and work; recommends traceable human review when agents modify knowledge bases.

AI-written summary · about

chapters (62)

  1. 0:00Start
  2. 0:05Session Opens - Working With Developers: A Tester's Survival Guide
  3. 0:36Speaker Intro - Wessel Braakman, Senior QA Consultant, Bouvet
  4. 1:41From the Netherlands to Norway, Plus Two AI Ethics Nonprofits
  5. 2:44Working With People Is a Jungle Because of the Species Involved
  6. 3:15The Four Types: Driver, Analyst, Supporter, Enthusiast
  7. 3:46Type One - The Driver: Decisive, Results-Driven, Wants Impact
  8. 4:17I Found a Bug in the Export Feature - Null Pointer Exception
  9. 4:47Does It Block Anything? Does a User Actually See This?
  10. 5:17If Nobody Uses It and It Bothers No One, Why Are We Talking?
  11. 5:50What Red Developers Need: Clarity, Confidence, Consequences
  12. 6:21The Second Attempt: Leading With "It Impacts 30% of Users"
  13. 6:52"That's Worth My Time" - Prioritised and Followed Up
  14. 7:24Why It Worked: Clear Impact and Showing You Understand What Matters
  15. 7:57Type Two - The Analyst: Detail-Oriented, Needs Evidence
  16. 8:28The First Encounter: "Something Weird Is Happening With the Spinner"
  17. 8:58"What Exactly Are You Seeing?" - and He Had No Steps Written Down
  18. 9:30Too Vague, No Evidence, No Reproduction - Conversation Over
  19. 10:01The Second Attempt: "I Found Something, I'd Like to Understand It Better"
  20. 10:34Half the Time the Spinner Doesn't Load - Here's the Screenshot
  21. 11:05Why It Worked: Context, Specifics, Evidence and Respecting Their Need
  22. 11:37Type Three - The Supporter: People-Oriented, Values Harmony
  23. 12:07The Developer Who Knows How Your Weekend Was
  24. 12:39The First Encounter: Handing Over a Diagnosis and a Line Number
  25. 13:09"Fix Line 142 and Let Me Know" - Effectively an Assignment
  26. 13:42This Time the Developer Was the One Who Felt Down
  27. 14:17The Second Attempt: "I Found Something and Wanted to Run It By You"
  28. 14:50Asking for Their Idea Instead of Delivering the Root Cause
  29. 15:22Treating Them as a Person, Not a Bug-Fixing Factory
  30. 15:54Type Four - The Enthusiast: Energetic, Idea-Driven, Bored by Routine
  31. 16:28The First Encounter: "What's the Idea Behind It?"
  32. 16:58What If We Redesigned the Whole Flow Instead?
  33. 17:30Imagine If We Added AI to It
  34. 18:00The Developer Who Shipped Ten Weekend Fixes Nobody Could Explain
  35. 18:31The Second Attempt: "I Found Something Super Weird - and Kind of Cool"
  36. 19:03Explaining Everything Already Tried, to Keep Them Engaged
  37. 19:33Offering More Ideas, Then Scoping the Work Together
  38. 20:09A Fun Session, Some Crazy Detours, and the Bug Fixed
  39. 20:39A Fifth Type Found More Recently - The Systems Thinker
  40. 21:13The First Encounter: "That Validation Is Also Used by the Import Flow"
  41. 21:45Focusing on a Local Fix to a System-Wide Problem
  42. 22:15Skipping His Own Thought Process Beyond His Application
  43. 22:45The Second Attempt: Arriving Knowing He Didn't Know the Dependencies
  44. 23:16Discovering the Import Flow, the Batch Job and One More Place
  45. 23:46Bringing Awareness of Risk, Not a Complete Answer
  46. 24:17Fixing It in a Way Compatible With Every Use Site
  47. 24:48Looking Back at the First Encounters
  48. 25:18Red Wasn't Dismissal - It Was Miscommunication
  49. 25:48Green: The Time He Pushed Too Hard and the Developer Felt Bad
  50. 26:19Yellow: A Powerful Tool That Needs Scope and Guidance
  51. 26:51How He Approaches All Five Types Now
  52. 28:23There Are Many More Personas Than These Five
  53. 28:54Where Each Type Shows Up in Your Team
  54. 29:24The Four Colours Are Loosely Based on DISC
  55. 29:55The Plan: More Comics, and Tester Types Too
  56. 30:57Q&A: Harder to Work With Developers or Business Leaders?
  57. 31:59Q&A: Aligning Developers and Business Leaders When Goals Conflict
  58. 33:01Q&A: Approaching Junior vs Senior Developers on Follow-Ups
  59. 34:33Q&A: Handling Requirement Managers and Extreme Requirement Lists
  60. 36:07Q&A: Which Type Should a Manual Tester Be?
  61. 37:39Q&A: Should Agents Modify the Knowledge Base They Learn From?
  62. 39:11It Has to Be Traceable, and Never Autonomous Without Oversight

related talks

~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.