Neil Taylor
Neil Taylor
Lead Quality Engineer
I've been testing for 20+ years with experience in Exploratory Testing and tools such as CI/CD, Bruno and Postman. I'm a self-taught pianist and enjoy writing and recording my own music.
🎂 MoTaBirthday | April 10, 2015
Open To
Meet at MoTaCon 2026
Write
Podcasting
7 Months ago today I wrote a moment about my goals for 2026 (My goals for 2026 | MoTaverse). In this post I wanted to provide an update and reflect on the year so far.Shortly after posting that mom...
13 Aug
Today has all been about learning new skills. But in this moment I wanted to talk specifically about AI skills. During the course of today I attended an excellent AI chapter event on AI skil...
30 Jul
On the 15th of January 2026 myself and Ujjwal Kumar Singh joined a call and pressed record. We were curious to see what would happen. A few weeks later I’d done the same with Neil Taylor and Clare ...
6 Jul
I believe this was TestBash Brighton 2016.If I recall correctly Deborah Reid did a 99 second poem, I could be wrong.In the back I recognise Emma Keaveny, Neil Taylor and Maaret Pyhäjärvi.Long live ...
3 Jun
Sometimes the most effective guardrail isn't the most sophisticated one
21 May
A lively episode about MoTaverse profile upgrades, MoTaCon momentum, AI-assisted testing, hidden knowledge silos, and why real human conversations still matter when tools move fast.
7 Aug
See why sharing small things often is one of the most effective ways to learn and grow in your career
23 Jan
Comments
(14)
Thank you to the MoTaverse Community
Bug Congrats Gary! Look forward to hearing all about your new role on a future TWiQ episode!
Call for Insights turns 45
Bug Congrats Simon!
It was a pleasure to be one of the first to have the chance to contribute to your new idea! 😀
Friction has a complex relationship with quality
Thank you both for sharing your conversation. The whole topic of the friction that can restrict and holds us back within a development team is definately worth exploring more. For me the biggest challenges I find are around the cognitive impact of too much context switching, managing conflicting priorities and getting a good balance between helping people and knowledge sharing.
Exploring My Reports
Thank you for sharing this Adam.
Some while ago I moved to recording testing sessions using VS Code and Markdown format (I like it as it works quite easily for screenshots and console output) and I've never quite settled on the categories to include in my report. I have to say I wasn't aware there was a Mark-map plug - but it gives a nice visual representation of the session! Also I like the way your template groups the findings.
Managing cognitive load for better software testing
Thank you for writing this article, as Gary mentioned many of us are no doubt facing similar challenges in our roles so its great you have explored this topic in detail. I certainly can identify with the challenge of too much context switching, it is especially a problem if you have a lot of product knowledge and it is important to find effective ways to manage it (for example sharing knowledge, protecting focused testing time.)
Learner finished your session
Reality bytes. Meet the teams and terms where they are
Community Star
3 days ago
Learner finished your session
Reality bytes. Meet the teams and terms where they are
Community Star
3 days ago
Learner finished your session
Reality bytes. Meet the teams and terms where they are
Community Star
3 days ago
