For me, testing software is not about following scripts or mastering tools, but about constantly questioning, investigating and learning.
I understand testing as a cognitive process where curiosity, systematic skepticism and contextual interpretation are the basis.
My principles:
- Testing is an intellectual activity: no “automated” thinking or delegated observation. Every test is a question about software behavior.
- Quality is not a step in the process, it is an ongoing conversation: I work with teams that see testing as a source of valuable information, not as a control barrier.
- Tools are secondary, reasoning is paramount: To automate without first exploring is to build on unvalidated assumptions. I prefer lightweight, adaptable tools that amplify - not replace - my judgment.
- The best tester is the one who improves the team's thinking: more than finding bugs, I help to develop critical thinking in developers, designers and stakeholders.
I look for teams that value uncomfortable questions, where “we don't know” is the starting point for discovery. If your priority is software as a product of collective reasoning (not as a finished artifact), let's talk.
Software Development
We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
"Lisa Crispin and Janet Gregory".
