Explore
- #jax london 11
- #test automation 9
- #java 8
- #architecture 7
- #infrastructure 6
- #developers 6
- #devops 5
- #automation 4
- #best practices 4
- #testing 4
- #culture 4
- #microservices 4
- #astro 3
- #node.js 3
- #software quality 3
- #information security 3
- #efficiency 3
- #principles 3
- #strategy 3
- #google-sheets 2
- #devcontainers 2
- #qa management 2
- #qa roles 2
- #cybersecuity 2
- #failure 2
- #distributed 2
- #coding 2
- #estimations 2
- #code quality 2
- #mermaid diagrams 1
- #mdx 1
- #docker 1
- #static site generation 1
- #framework 1
- #cms 1
- #virtualization 1
- #local environment 1
- #error handling 1
- #expo 1
- #android 1
- #react 1
- #web development 1
- #virtual 1
- #safe box 1
- #proxmox 1
- #vpn 1
- #cia triad 1
- #software 1
- #recruitment 1
- #dsl 1
- #junit 1
- #streaming 1
- #cynefin 1
- #complexity 1
- #happines 1
- #goals 1
- #events 1
- #resilience 1
- #aggregates 1
- #cqrs 1
- #event sourcing 1
- #innovation 1
- #test framework 1
2016
The three QA amigos: SDTs, AEs and the VBEs
A usual misunderstanding among many teams is to regard testing as one team without any specialization. Moreover, the biggest mistake that I have seen is to give the same job title to all "testers" regardless their skills and contributions.