Jonathan Cole
Jonathan Cole
Tester
Tester with two decades of EPOS experience. A Domain Expert and Cross鈥慒unctional Generalist focused on quality, clarity, and continuous learning. Currently developing automation skills across Web Apps, WPF desktop applications and API testing.
馃巶 MoTaBirthday | September 17, 2024
Ady Asks the MoTaverse. Hi everyone, thank you for your great feedback on the first draft of this chapter. I've taken your thoughts, feedback, and ideas on board and here is the updated version. I'...
14 Oct
My first time at OHSO and what a lovely experience! I got to meet loads of famous people and some upcoming stars too. The Motaverse is full of friendly, interesting people with unique stories to te...
30 Sep
1,000 songs in your pocket changed how the world listened to music. The MoTaverse changes how tech professionals grow their careers.Sixteen features, sixteen stories, one thread running through al...
26 Aug
As a tester working in a small team, I often found myself using skills that I couldn鈥檛 easily name or evidence. When our company was taken over by a larger organisation, I needed to align myself w...
29 Jul
Master the RICCE framework to transition from manual testing to AI-augmented automation by leveraging structured prompting and the Playwright MCP agent ecosystem.
9 Apr
Comments
(2)
Ady asks the MoTaverse #4 Mindset chapter draft
If the chemotherapy example is a bit heavy, my washing machine provides a more everyday example. It beeps repeatedly when a cycle finishes while I'm sat comfortably watching TV. I always find myself wondering whether anyone considered the user's perspective and asked, "Does this really need to be this annoying?" It does its job, but perhaps not with much empathy for the person experiencing it.
Ady asks the MoTaverse #4 Mindset chapter draft
I used AI to tidy up my thoughts, hope that's ok. I found it both useful and interesting. My initial thought was, "This is great, if only we were always given the time and space to think this way." In many organisations there's pressure to get something out quickly because "that will do" or "we can improve it later". I appreciated the practical suggestions. They recognise reality and give people a way to start changing mindsets.
The chapter made me think beyond software. When my dad was having chemo, the drip machine emitted a harsh alarm that wasn't always urgent. I remember wondering who tested that experience, getting into the shoes of the users is so important. One observation: Terms like "3 amigos", "backlog refinement", "sprints" and "pull requests" may not be familiar to everyone. Some testers work on desktop apps and the like. A brief explanation might help. In a way, that's applying the Inclusive Mindset to the readers too right. Overall, it made me want to read more.