Two MoTacon attendees are on the left. The MoTaacon logo is in the center, and to the right a prompt to Get Your Ticket.
The New SDLC With Vibe Coding image
Google has shared a short whitepaper, only 51 pages long, on the use of AI in software development. It is very well written, with almost no fluff. If you want to get a very high-level foundati...
Four Ds of effective AI usage (AI Fluency Framework) image
If you, fellow tester, work with AI, remember the four 4 Ds: To delegate tasks for AI, we need to know about the capabilities and limitations of AI tools and models To describe tasks for AI, we ne...
What's the hardest part of defining "expected behaviour" for a system that produces different output every time? image
  • Piotr Wicherski's profile image
  • Simon Tomes's profile image
  • Oleksandr Romanov's profile image
  • Lauren Lassey's profile image
  • Jesse Berkeley's profile image
  • James Pearce's profile image
  • Adam Davis's profile image
  • Demi Van Malcot's profile image
When a system improvises like a jazz soloist, "different" stops meaning "wrong"
Hot, flaky, and unfinished - Testing, accessibility, and the grief we don't talk about - Ep 137 image
  • Simon Tomes's profile image
  • Ady Stokes's profile image
  • Oleksandr Romanov's profile image
  • Clare Norman's profile image
  • Judy Mosley's profile image
Judy and Clare trade spicy hot takes, from notification overload and 'done > perfect' learning, to a passionate deep dive on accessibility as a moral (and business) imperative.
Hot take: if you're surprised by a product behaviour, you don't understand the system enough image
  • Oleksandr Romanov's profile image
  • TWiQ — This Week in Quality's profile image
Oleksandr said: My hot take of the week: If you don't fully understand the thing you want to test and measure - you might get the results that are surprising but yet mysterious. So - first - unders...
Subscribe to our newsletter