Skip to main content

Why? Why? Why? The questions of a 2 year old AND Testers!

Apologies for the lack of blog posts, but for those that don't know me, not only am I a struggling Tester, but also a struggling Parent! I have 2 kids, a 2 year old and a (soon to be) 5 year old! They are my world, and they're also the inspiration for some blog posts that I tend to write, this latest one is no different...



My 2 year old daughter has begun to question a lot of what I say to her.

"Please don't climb up the slide"

"Why?"

"Because the slide is slippery and you might hurt yourself"

"Why?"

"Because it rained last night"

Ad infinitum!

My 5 year old said to me and Jess the other day "We mustn't ask "Why?" must we because that is answering back" I thought to myself, I don't want him to stop asking Why? to stop asking "What If?" This is a massive skill and something we as Testers should definitely have and encouraged. So I had to explain to him that it's not a problem to ask "Why?" it isn't answering back, if you genuinely don't understand something, then you need to be able to ask "Why?" without fearing anything happening to them.

The last thing I would want to suppress, both in Testers at work and my children at home is the freedom and the environment in which they can ask questions and they can question anything without fear of being laughed at or being told off.

Sure there are times when the questioning becomes too much (especially from the kids!), or it's at an inappropriate time, but that applies to life in a Development team as well. You don't want to be questioning things at the very end of something, similar to finding bugs, the earlier you can ask questions the easier they are to answer and hopefully react upon.

I genuinely believe that there is no such thing as a "Stupid question" but also that sometimes the most silly questions are really good questions and can throw up some confusion around what is being developed. If we don't question things, then we won't improve and we'll stay the same!







Comments

  1. I agree with you many silly questions really have some positive impact plus some positive answers too. And I think the ones who do silly questions are the real intelligent people.

    ReplyDelete

Post a Comment

Popular posts from this blog

Testers: Be more like a Super-Villain!

Who doesn't love a Super Hero? Talk to my son, and he'll tell you how much he loves them, talk to many adults and they'll say the same! Deep down, we all love to be the Super Hero, we all want to save the day! However, I want to talk about the flip side of Super Heroes, the Super Villains... I often play Imaginext with my son, and I (unfortunately?) am nearly always the Super Villain! Be it Lex Luthor, Joker, Two Face, Mr Freeze or The Riddler! These are all great characters and great Super Villains, but why would I want to write about Super Villains? A while ago where I worked, we had a few Super Heroes, people who would be able to come in and "fix" things that had broken and help deliver projects on time. We then shifted, we decided to do away with the Super Hero culture and try and prevent from being in that position in the first place, whilst we didn't go as far as wanting to hire Super Villains, it's definitely a story that has stuck with me and t...

QA is Awesome!

No real point to this post other than I have had the song stuck in my head and figured I could change it slightly and quite easily make QA is Awesome! Oh and I haven't even seen the movie all the way through! But for some reason that song is incredibly catchy! Not much point to this post in fact, just thought I'd put it out there :)

Measuring QA Key Skills and Competencies

I have been thinking about how I can help encourage self improvement within my team, as I understand it, everyone wants to improve, it's just that often there are a number of things that hold people back. I believe one of these things that hold people back are around identifying skills that they are perhaps weak in or that they could/should improve on. So I thought about how I can help tackle that problem. One solution that I want to try with people is to identify the key skills for a QA, what key skills should every QA have, or at least what key skills make up a good QA? If I can identify these then I can start helping people identify if they are lacking in an area. Sure there is a competency matrix that we have, but it has things like "An excellent understanding of XXX", it's often very difficult to quantify what an excellent understanding actually is. So I sat down and came up with the following key skills: OOP Test Documentation Manual Testing Automated...