“Why would I need to learn about architecture? I just work on tickets.”
“I don’t just want to push tickets across the board, but what can I do?”
- Open as many doors as possible – the more doors opened, more chance to walk through them. Literally no one can walk through one for you.
- Promote questions and not answers – buckets of detail lead to buckets of dependence and dogma. Careful.
- Not obsessed with definitions – defining things is useful, until it becomes divisive. See ‘Testing vs Checking’ when used as a stick. Socially generated definitions in organisations through conversation. Useful.
- Represent the core of a tester – what are the core skills of a tester. Now thats an interesting question. Choose wisely from the multitude. Discuss.
- Was your career linear? – did your career progress beautifully along a smooth curve? Bullshit. Career models generally ignore the bumpiness of reality. And are created by managers who do not listen to their own experience.
- More you learn, the less you know – testing is a vast discipline, which is part of its allure. I have no idea how much I don’t know. Each segment of the wheel could be a specialism/career in learning in itself.
- Disciplines overlap as much than they differ – create something that developers. product people recognise too? Similarities as well as differences are important.
- For the buccaneers – ever seen an organisational career model which reflected never mind rewarded buccaneering learning? They are generally about finishing stuff not learning stuff through broad horizons.
Then, the wheel was then born! Gandalf wasn’t there. Or Dumbledore. Just me. More soon.
Original slides from NWEWT2:
Had a great time debating “Growing Testers” at #NWEWT. Slides from my “Bullseye” report are here! #testing https://t.co/LJXpUOJefh
— Ash Winter (@northern_tester) March 20, 2017