Continuing with an experiment. Let's look at the talk and workshop descriptions of MoTaCon 2026 and share my thoughts and reflections before the talk/workshop has happened. And then, hopefully, sh...

I've never done a proper podcast, yet here I am.20 episodes in.Weekly cadence.Great quality conversations.Catching up with old friends.Making some new ones.100% stepping outside of my comfort zone....

Shift‑left security: building protection from day one The hidden leadership of Quality Professionals: skills you only earn when everything goes to hell When systems stop behaving: controlled chaos...

The lineup is out and oh my... how exciting is it?These are the contributors we've announced publicly... but let me tell you something. Every single person walking through the Brighton Dome doors b...

Coming all the way from New York to Brighton, we're very happy to announce that Susanne Abdelrahman will be joining us at MoTaCon to answer this head-on in her talk: Can we actually co-own quality?...

One of the biggest motivations for me with the MoTaverse is simply to make an excuse to meet, catch up, geek out and make friends.I connected with Susanne Abdelrahman via the MoTaverse. Then along ...

An honest conversation about care, influence, and the ripple effects of doing quality work when nobody has to listen to you.

Mobbing is a collaborative software development and testing technique where an entire team works on the same task, at the same time, in the same space (physical or virtual), and on a single computer. It extends the concept of pair programming to the whole group, including developers, testers, product owners, and other stakeholders.One person acts as the "driver" (controlling the keyboard/mouse) while others serve as "navigators" (providing direction), with frequent rotation of roles to keep everyone engaged. The practice uses "strong-style navigation" where the driver follows guidance from the navigators. This ensures all ideas flow through the group and creates shared understanding in real-time. Mobbing applies to many activities: Mob programming involves teams collectively writing code, making design decisions, and solving complex technical problems together Mob testing brings diverse perspectives to exploratory testing, test automation, or bug investigation, combining domain knowledge, technical skills, and testing expertise Mob learning uses the format for onboarding new team members, learning new technologies, or tackling unfamiliar problems where collective knowledge accelerates understanding Benefits of mobbing: Eliminating Handoffs: Tasks are completed in one pass (writing, testing, and reviewing happen simultaneously), which significantly reduces "Work in Progress" (WIP) and cycle time. Knowledge Sharing: It is one of the fastest ways to spread technical and domain knowledge across a team, preventing "silos" where only one person understands a specific feature. Higher Quality: With "many sets of eyes" on the code as it is written, technical debt and bugs are often caught and fixed instantly. Team Building: It builds mutual respect through meaningful, mission-critical work rather than artificial exercises. Common challenges: Intensity: Constant collaboration can be mentally draining and may not suit all personality types. Cost Perception: May be seen as "inefficient" because multiple people are working on the same thing, though proponents argue the higher quality and lack of rework offset this. Dominant Personalities: Stronger voices may overshadow others if the group does not strictly adhere to inclusive "kindness, consideration, and respect" rules.