Generally this blog is about original material. However, once in a while I will find something so extraordinary that I just want to link to it, and "keep it" on the blog - so I and other readers can come back to it.
I don't do it often, but when I do it's because it either so moved me, or I have an absolute need to say "+1" to it. Here I look at some recent TED talks which have completely blown me away for one reason or another ...
How the worst moments in our lives make us who we are
Here Andrew Solomon talks about people who have had to deal with adversity. In particular how those who transcend show an ability to forge meaning in their trials ...
https://www.ted.com/talks/andrew_solomon_how_the_worst_moments_in_our_lives_make_us_who_we_are#t-1195138
[If you only have time for one talk, this is the one I'd recommend]
How frustration can make us more creative
A recommendation from my parents no less! How well they know their son.
Contrary to what me might seem common wisdom - it's often when we're just a little uncomfortable. When thinks are a little disorganised and maybe even chaotic. These are the time we're actually much more switched on and creative ...
https://www.ted.com/talks/tim_harford_how_messy_problems_can_inspire_creativity
Really "mixing it up a bit" and Brian Eno's Oblique Strategies sound useful for many an agile team.
Trial, error and the God complex
Economist Tim Harford looks at complexity in the world, and the "God complex" trap - where we think we understand things, and try and simplify our approach. He argues that we evolve our approach best by adding a bit of randomness and taking a trial and error approach.
This really resonated with me. Recently I took part in James Bach's challenge on integration testing. He set a problem, and I gave how I'd approach testing it. When he asked me why I'd do some of it - what problems I'd expect to find, I was tempted to change my scope, and do less. But he reminded me you don't always have to justify everything - if a test is simple, and is there out of curiosity, don't feel the need to justify every test you do.
Likewise in agile, we'll test functionality around a story, because we know that's where the most change has been. But sometimes we want to test manually in areas we know haven't changed. The God complex tells us that area hasn't been changed (that we know of), so it's a waste of time testing. However, once in a while, we find something has got through - and our God isn't as infallible as they led us to believe. Trial and error will find things that God complex cannot anticipate, and it's an important tool for us a testers!
https://www.ted.com/talks/tim_harford
[This talk echoes some themes I'm encountering reading Thinking Fast And Slow]
Sunday, March 13, 2016
WRITING 104 - Lessons from Jasper Fforde
This week just happens to be "Writers Week" in Wellington and I managed to get to a talk by Jasper Fforde on his experiences as a writer.
I seriously love Jasper's work - like Terry Pratchett, he creates books that are surreal flights of fancy, but with their own internal logic. My favourite are probably the Reading Nursery Crimes - a procedural crime thriller with a nursery rhyme twist. Or indeed the alternate world of "Thursday Next", where England was invaded by Germany, President George Formby led a rebellion, Wales became a socialist republic, and everyone is fanatical about plays and books - to the point where there are shades of literary hooliganism, with occasional violent clashes between fans of respective authors.
As this fits in nicely with the current theme of writing, I thought I'd provide a quick summary of what he had to say. Firstly, as he pointed out, story is something that's incredibly powerful to us as human beings. We love to share stories - whether it's around the campfire as early cavemen or around the office watercooler. Indeed, most of our learning is wired into storytelling - which links into my tale last time of examplification - we can often remember a tale far longer than the "moral of the tale" alone.
Think about why the stories of Shakespeare, which remaind enduring in one way or another, even though the language is dated - because people are still falling in love with people they shouldn't (Romeo and Juliet), driven by insane jealousy (Othello), being led astray by flattery over truth (King Lear) or just generally going into forbidden jealousy and becoming the playthings of supernatural spirits (Midsummer Night's Dream).
Even if I was to say to you "be a good Samaritan", it only has meaning because of the story in the Bible. And the story was one Jesus used himself to illustrate the concept of being a neighbour to another - in the biblical context the Samaritan was a different creed to the man who was robbed on the road.
[As a side note - I also thing that defects always work more powerfully as well if we talk about them as a story of sorts]
Much like any workshop with any writer, an all-too-common question came up about "how do you become a writer"?. Jasper was interesting on this - his writing has a good understanding of literature, and I've always assumed he'd studied English at University. Wrong - he had been a school dropout.
After school he'd worked as a focus puller on movies, and had become interested in maybe writing a film one day. So he started to try and write - and initially he was terrible. He'd mainly write short stories - but he found that he really enjoyed doing it.
Many people want to know if there's an easy way to be a writer - but there's no short cut. Just like there's no short cut to becoming a marathon runner. But you can become one in the same way.
Can you run a marathon now? I'd assume the answer is no. Could you be able to? Assuming you have two good legs and decent enough health - quite probably. But you'd have to practice - run a few times a week, just whatever you were comfortable. If you wanted to get really good, you might want to see how other people run, and try mimicking them. You might even want to film yourself running and see if there's anything you need to modify.
Jasper's advice was similar - write, and enjoy writing. Read back some of your old stuff - be prepared to be critical, and always ask "how could I make this better?". Read other people's fiction, maybe even play around with mimicking some of their writing, and find out if it feels comfortable to you. Every time you apply this, you'll get a little better and better. You'll make the odd typo and do their/their/they're wrong occasionally, but don't beat yourself up too much. Revisit your material several times before passing it on.
For myself, I preferably leave an article a few days or a week before rereading. At bare minimum have a coffee and a context break before rereading. For a standard blog piece, I reread an article about 3 times before it gets published (it's about 5-10 reads for anything in a book). I particularly have noticed if I work on something over several days, everytime I "take a break" I pick up in a slightly different style. Sometimes I'll have said the same things several times, without noticing. It can all be smoothed.
Sometimes I'll royally get stuck, and will email a friend what I have so far and ask for ideas advancing it - sometimes I'll use Twitter.
In a style similar to testing - I'll reread a couple of times until I can't find any other mistake to smooth. Even so I'll sometimes reread months later and see a their/there/they're calamity!
But as Jasper reminded us all - most of all have fun!
Thursday, March 10, 2016
It should be International Celebration Day ... EVERYDAY
So this week was International Women's Day - look it up here, it's a thing. And yes, there's an International Men's Day too if you're worried. Although to me, International Talk Like A Pirate Day sounds much more fun (I need to remember next year).
What I thought was quite nice, there were some folk on Twitter thanking and celebrating women they'd felt had been influential. The problem is - if you missed it, then I guess you need to wait 365 days til next year to celebrate someone you thought was influential. Heck, less if that person is male!
Or maybe you can tell them right now? Or let the world know right now? What's stopping you? Do you REALLY need a special day to do it?
Celebrating people in our life is something I think we can be really crap about. It's "not cool", and certainly something as a teen-uncomfortable-with-emotion brought me out in a sweat. It's unfortunate, but it took something sad to snap me out of it.
I've talked before about my grandmother who died in 2014. She was very dear to me, but I couldn't always say it. Sadly she was diagnosed with early Alzheimer's the week before I got married - it was an absolute bombshell for me - I realised she wouldn't be around forever. But as sad as that realisation was, it led to something good. It made me realised that saying "I love you", holding her hand, hugging her as long as I could - it was all important, and it made her day. And as hard as losing her in 2014 was, there are no major regrets - and those memories you have are all the "warm fuzzy kind". You only regret there wasn't room for an extra one or two.
I guess I must have got into the habit - when my friend Violet died unexpectedly in 2010, I was obviously sad, and continue to be. But I know I told her how important she was, and said all those important things that need to be said between best friends.
Make celebrating people and being thankful for them something you don't wait to be prompted for "a special day" to do.
What I thought was quite nice, there were some folk on Twitter thanking and celebrating women they'd felt had been influential. The problem is - if you missed it, then I guess you need to wait 365 days til next year to celebrate someone you thought was influential. Heck, less if that person is male!
Or maybe you can tell them right now? Or let the world know right now? What's stopping you? Do you REALLY need a special day to do it?
Celebrating people in our life is something I think we can be really crap about. It's "not cool", and certainly something as a teen-uncomfortable-with-emotion brought me out in a sweat. It's unfortunate, but it took something sad to snap me out of it.
I've talked before about my grandmother who died in 2014. She was very dear to me, but I couldn't always say it. Sadly she was diagnosed with early Alzheimer's the week before I got married - it was an absolute bombshell for me - I realised she wouldn't be around forever. But as sad as that realisation was, it led to something good. It made me realised that saying "I love you", holding her hand, hugging her as long as I could - it was all important, and it made her day. And as hard as losing her in 2014 was, there are no major regrets - and those memories you have are all the "warm fuzzy kind". You only regret there wasn't room for an extra one or two.
I guess I must have got into the habit - when my friend Violet died unexpectedly in 2010, I was obviously sad, and continue to be. But I know I told her how important she was, and said all those important things that need to be said between best friends.
Make celebrating people and being thankful for them something you don't wait to be prompted for "a special day" to do.
Tuesday, March 8, 2016
WRITING 103 - Examplification ...
In the last couple of weeks I've reviewed two articles for people - ironically both called Simon. [One is Simon my brother, one is Simon who I talked about previously]
Now, they'd both written very good pieces. But from applying a simple suggestion from me, they managed to raise the bar. They'd written some very good theory, but in order to convey something about that theory, they really needed an example.
Examples are a great way of getting a point across, and one of my simple things to consider when writing. I'm reading some critical thinking books at the moment, and I heavily rely of the examples as a great way of showing the nuts and bolts of a concept.
Indeed, Lisa Crispin told me during writing More Agile Testing that the "sidebars" of people's experience reports during her first Agile Testing book had been one of the most successful point of her and Janet Gregory's book. I had to agree - agile was such a radical concept when I first read it, and the experience report examples really helped me to get to grips with some of the ideas!
Often within this blog, I'll talk about an idea, and use a kind of cultural shorthand - picking out an example from a popular film. This makes things easier for me, because I try and take something you're already familiar with, and analyse it - it makes the storytelling easier for me.
Now that'a good for semi-familiar concepts - I for instanced used Star Wars to talk about team building in this post. However there's also a danger of alienating the reader - as Dan Billing warned me in a private discussion. If the reader isn't familiar with the media piece you're using, then they'll go "huh?" and you lose everything.
Of course the best kind of example is when you take it from your own life, and apply suitable "anonymity" to the tale that you don't risk damaging relationships with someone or needlessly calling someone out/damaging their reputation. I generally anonymise stories - with the exception of the odd Rex Black antic or indeed when I finally said "enough's enough" about Bob Marshall's behaviour.
Generally for each point just a single example will do. If the point is a main theme, you might want up to about three examples, each offering something a little different. Avoid different examples which don't offer anything new from each other.
Here's an exercise for you. You've just written the words "we all know it's important to test early" - now back it up,
Enjoy - and get practicing!
Now, they'd both written very good pieces. But from applying a simple suggestion from me, they managed to raise the bar. They'd written some very good theory, but in order to convey something about that theory, they really needed an example.
Examples are a great way of getting a point across, and one of my simple things to consider when writing. I'm reading some critical thinking books at the moment, and I heavily rely of the examples as a great way of showing the nuts and bolts of a concept.
Indeed, Lisa Crispin told me during writing More Agile Testing that the "sidebars" of people's experience reports during her first Agile Testing book had been one of the most successful point of her and Janet Gregory's book. I had to agree - agile was such a radical concept when I first read it, and the experience report examples really helped me to get to grips with some of the ideas!
Often within this blog, I'll talk about an idea, and use a kind of cultural shorthand - picking out an example from a popular film. This makes things easier for me, because I try and take something you're already familiar with, and analyse it - it makes the storytelling easier for me.
Now that'a good for semi-familiar concepts - I for instanced used Star Wars to talk about team building in this post. However there's also a danger of alienating the reader - as Dan Billing warned me in a private discussion. If the reader isn't familiar with the media piece you're using, then they'll go "huh?" and you lose everything.
Of course the best kind of example is when you take it from your own life, and apply suitable "anonymity" to the tale that you don't risk damaging relationships with someone or needlessly calling someone out/damaging their reputation. I generally anonymise stories - with the exception of the odd Rex Black antic or indeed when I finally said "enough's enough" about Bob Marshall's behaviour.
Generally for each point just a single example will do. If the point is a main theme, you might want up to about three examples, each offering something a little different. Avoid different examples which don't offer anything new from each other.
Here's an exercise for you. You've just written the words "we all know it's important to test early" - now back it up,
- Come up with an example of testing late, and how it stung?
- Have you ever found a problem in software early on? Did you feel you stopped a major overspend?
Enjoy - and get practicing!
Wednesday, March 2, 2016
WRITING 102 - the "R" word ...
In Back To The Future - Marty McFly goes back in time, and meets his father as a teenager. He's somewhat shocked to find George McFly writes stories. At the time George's words really struck a chord with me ...
George refused to let anyone else see his writing because, as he puts it, “What if they don’t like it? What if they think I’m no good? I just can’t take that kind of rejection!”
In this article I'm going to tell you about some of my rejection tales - partly so I exorcise some personal demons, but also to really take the sting and fear out of it for you.
Eeek - it got personal!
I never really saw myself as a writer, but back in 2006, I met up with a group of friends who like me were Doctor Who geeks, and enjoyed making Doctor Who themed audios. I starred in one of those dramas, which you can find here.
The problem came though when I was approached to write a story myself. I wrote several. And numerous rewrites ... which were then "dropped". Sad to say, I did take it very personally (not helped by the fact that they decided not to tell me that decision, until I flat-out asked "when are we recording one of mine?"), and it did cause a lot of friction between us all.
But here's the good news. I never saw myself as a writer until then ... but then I had a feeling of "something to prove". Which pretty much "lit a rocket up my arse" to get writing within testing, and led to the first publication on this blog in 2010.
Don't be afraid!
So I started blogging here in 2010 - and I tried to blog regularly. Initially my blog reader count, and the Twitter account I used to promote was pitiful. I was learning as I went.
But with each post, I got better. As I found when I used to run a comedy blog in the early 2000s (the material for which is too dire to reproduce), the more I wrote, the easier it got.
Soon enough I got a desire to get published in The Ministry Of Testing's Testing Planet. I even ended up getting a position on the editorial staff. Simples, yes?
Actually, no. I actually got my first three submissions rejected, On the plus side, you could say there wasn't a culture of favouritism to the staff going on. It was a little frustrating for me, especially because as a reviewer I did everything I could to work with a writer to get their article to a publishable state. And I did feel a little like I wasn't being extended the same courtesy.
However, there were multiple reasons,
Thankfully Testing Planet owner Rosie Sherry knew that at three rejections, it was probably my limit before I just gave up and stopped submitting. So she handed me to the very capable hands of new editor Simon Knight, who worked with me through my Schrodinger's Code article to produce something on a similar theme, but exploring it in a different way to Elisabeth.
He asked questions, asked for elaboration, asked for clarity .... it was a fun experience, of writing, and being challenged to push myself further. The end result was an article called "The Software Minefield". To be fair, the article was better than what I was capable at the time, and it led to a good friendship between myself and Simon. I eventually was even given an article by Simon to review - submitted under a pseudonym so I wouldn't show favour!
If the price of three rejections was the price of getting to know Simon, it was well worth the price of admission. I learnt a lot about pushing myself as a writer from him. I also learned a lot about editing from him. In fact I'd not have been as good supporting More Agile Testing as a reviewer if not for Simon.
It also led me to the ultimate accolade, where my brother (another Simon) asked me for his help writing an article on change management. Sibling rivalry is a force to be reckoned with - just ask Cain and Able!
Ultimately, what I'm saying is, don't fear rejection. Dare to write - but don't be afraid to ask someone "I'm new to writing, this if what I've got, any hints?". With luck you'll find your own Simon Knight to help you become the better writer!
George refused to let anyone else see his writing because, as he puts it, “What if they don’t like it? What if they think I’m no good? I just can’t take that kind of rejection!”
In this article I'm going to tell you about some of my rejection tales - partly so I exorcise some personal demons, but also to really take the sting and fear out of it for you.
Eeek - it got personal!
I never really saw myself as a writer, but back in 2006, I met up with a group of friends who like me were Doctor Who geeks, and enjoyed making Doctor Who themed audios. I starred in one of those dramas, which you can find here.
The problem came though when I was approached to write a story myself. I wrote several. And numerous rewrites ... which were then "dropped". Sad to say, I did take it very personally (not helped by the fact that they decided not to tell me that decision, until I flat-out asked "when are we recording one of mine?"), and it did cause a lot of friction between us all.
But here's the good news. I never saw myself as a writer until then ... but then I had a feeling of "something to prove". Which pretty much "lit a rocket up my arse" to get writing within testing, and led to the first publication on this blog in 2010.
Don't be afraid!
So I started blogging here in 2010 - and I tried to blog regularly. Initially my blog reader count, and the Twitter account I used to promote was pitiful. I was learning as I went.
But with each post, I got better. As I found when I used to run a comedy blog in the early 2000s (the material for which is too dire to reproduce), the more I wrote, the easier it got.
Soon enough I got a desire to get published in The Ministry Of Testing's Testing Planet. I even ended up getting a position on the editorial staff. Simples, yes?
Actually, no. I actually got my first three submissions rejected, On the plus side, you could say there wasn't a culture of favouritism to the staff going on. It was a little frustrating for me, especially because as a reviewer I did everything I could to work with a writer to get their article to a publishable state. And I did feel a little like I wasn't being extended the same courtesy.
However, there were multiple reasons,
- My first article, "The Agile Haka", had already been published on this blog, and there was an "exclusive content" clause. [Be aware of this for some places]
- My second article "The View From The Test Manager's Gallery" was written exclusively for publication on test management, but rejected by Rob Lambert for being too long for the paper. I was kind of gutted, but Testing Circus got behind me to publish it.
- My third article "Schrodinger's Code" was alas too derivative of an article by Elisabeth Hendrickson. I sometimes feel guilty I don't credit Elisabeth more. I think although I don't try and emulate her, her writing style has been extremely influential on me - more than any other software testing writer. Because she taught me to embrace storytelling, and it is okay to be off the wall. I'm really saddened as you can imagine that she doesn't have as much time to write these days.
Thankfully Testing Planet owner Rosie Sherry knew that at three rejections, it was probably my limit before I just gave up and stopped submitting. So she handed me to the very capable hands of new editor Simon Knight, who worked with me through my Schrodinger's Code article to produce something on a similar theme, but exploring it in a different way to Elisabeth.
He asked questions, asked for elaboration, asked for clarity .... it was a fun experience, of writing, and being challenged to push myself further. The end result was an article called "The Software Minefield". To be fair, the article was better than what I was capable at the time, and it led to a good friendship between myself and Simon. I eventually was even given an article by Simon to review - submitted under a pseudonym so I wouldn't show favour!
If the price of three rejections was the price of getting to know Simon, it was well worth the price of admission. I learnt a lot about pushing myself as a writer from him. I also learned a lot about editing from him. In fact I'd not have been as good supporting More Agile Testing as a reviewer if not for Simon.
It also led me to the ultimate accolade, where my brother (another Simon) asked me for his help writing an article on change management. Sibling rivalry is a force to be reckoned with - just ask Cain and Able!
Ultimately, what I'm saying is, don't fear rejection. Dare to write - but don't be afraid to ask someone "I'm new to writing, this if what I've got, any hints?". With luck you'll find your own Simon Knight to help you become the better writer!
The Software Minefield
This article was originally published in The Testing Planet magazine, as was the titular piece of my first book, The Software Minefield.
Let me take you on a journey...
You are with a party of friends on a beautiful walk in the countryside. It's a lovely day, and according to your map you are making good time. Some time soon you should arrive at your destination - a café which has come highly recommended to you. You can almost smell the coffee and cakes now!
As you open a gate a sheep accidentally comes through, and soon bounds off in front of you. Imagine the total shock when with a sudden BOOM it explodes before your eyes. It's at that moment you realize that although you didn't intend to, you've somehow entered a minefield.
Suddenly your beautiful day has become treacherous and your good progress has lead only into peril. The only way you'll get out alive is by making good decisions from here on in.
There is no doubt that software development echoes this parable in many ways, especially when it comes to testing. Our projects can often seem to make good progress, but little do we realize we're just getting ourselves deeper into a minefield.
As testers we can often feel much like that rambler, we know there's peril out there in the form of defects, but we're not sure where exactly and of what severity. But often to the rest of our party the wake up call will only come when the first mine has gone off ...
How do we best deal with minefields? And how can we apply that to software?
One approach would be just to back up and hammer a sign (okay, being very careful where we hammered it) to warn "Caution Minefield". Then we can quite happily state that anyone entering does so at their own risk, and we did warn them. Some companies have indeed taken this attitude with customers, saying "well our customers will let us know if they find any problems". The problem with letting customers loose in a minefield is that you could soon find yourself running short of customers...
In a similar vein, we can follow the example of history, and drive a flock of sheep over the field, and find problems that way (helps to have a bottle of mint sauce handy though). This can be what happens when we let loose 'end users' on our system in a controlled way, and "if it doesn't fall over it must be okay ... but no people will be harmed". This is rather quick and dirty way to test, and although it should find a lot of problems, it's rather random, and not guaranteed to make it completely safe. Who knows what bits the sheep might be avoiding ... indeed the sheep may have a mentality towards self-preservation the shepherd isn't aware of. Maybe the grass above a land mine just isn't juicy and fresh enough to tempt a sheep.
Much better is to bring specialist mine hunters or engineers in to clear a path. They will need some expensive equipment like metal detectors to probe ahead, and when a mine is found, they need to work with an expert to remove and defuse it. But this is slow and methodical work, with everything almost grinding to a halt when a big problem is unearthed. In the story above, as your engineers clear a path, there will be someone who will complain it's too slow and the café will be closed by the time you're across the field.
And though you'll have cleared a path, it may still not be safe. Your friend needs to go to the toilet behind a bush whilst this is going on, but that involves stepping off the safe path. When can you declare a field safe and move on? Do you keep going backwards and forward with your engineers until you've covered every square inch? Do you cover the main footpaths first? Or can you claim it safe if you've not found any mines for the last couple of hours?
How can you ever really be sure? It's easy to know about the presence of mines - they have a way of making their presence known - but how can you be confident of their absence? How can you be sure that as you're unearthing mines in one part of the field, some scoundrel isn't laying new ones in the other end (ooh, and you thought the minefield was static - that could be a dangerous assumption)?
That question is of course one that applies to testers, managers, developers. How can you be sure you've de-mined your software of defects? Of course you never can be sure, but it doesn't hurt to have covered as much ground as possible. Every mine you find makes the field safer.
In reality we tend to bring in our specialist demolition engineers, our Testers to check methodically as many paths as possible. Then to cover ourselves, we bring in our users for acceptance, and send out the sheep ...
As with so much in life there's no "one way" to solve this problem scenario.
There's really no way to one way, no right way to solve this. You have a drive to get somewhere (your café). But you can easily spend the rest of your life going backwards and forwards in this field before you can declare it safe. Of course if you're careless, you will be spending the rest of your life here.
At the end of the day, the most important thing is we and everyone in our party respects that we're in a minefield, and act accordingly. Not letting our leaders persuade us "you're all being silly, it's just one mine, c'mon follow me, they'll be out of meringues if we dawdle ...".
Let me take you on a journey...
You are with a party of friends on a beautiful walk in the countryside. It's a lovely day, and according to your map you are making good time. Some time soon you should arrive at your destination - a café which has come highly recommended to you. You can almost smell the coffee and cakes now!
As you open a gate a sheep accidentally comes through, and soon bounds off in front of you. Imagine the total shock when with a sudden BOOM it explodes before your eyes. It's at that moment you realize that although you didn't intend to, you've somehow entered a minefield.
Suddenly your beautiful day has become treacherous and your good progress has lead only into peril. The only way you'll get out alive is by making good decisions from here on in.
There is no doubt that software development echoes this parable in many ways, especially when it comes to testing. Our projects can often seem to make good progress, but little do we realize we're just getting ourselves deeper into a minefield.
As testers we can often feel much like that rambler, we know there's peril out there in the form of defects, but we're not sure where exactly and of what severity. But often to the rest of our party the wake up call will only come when the first mine has gone off ...
How do we best deal with minefields? And how can we apply that to software?
One approach would be just to back up and hammer a sign (okay, being very careful where we hammered it) to warn "Caution Minefield". Then we can quite happily state that anyone entering does so at their own risk, and we did warn them. Some companies have indeed taken this attitude with customers, saying "well our customers will let us know if they find any problems". The problem with letting customers loose in a minefield is that you could soon find yourself running short of customers...
In a similar vein, we can follow the example of history, and drive a flock of sheep over the field, and find problems that way (helps to have a bottle of mint sauce handy though). This can be what happens when we let loose 'end users' on our system in a controlled way, and "if it doesn't fall over it must be okay ... but no people will be harmed". This is rather quick and dirty way to test, and although it should find a lot of problems, it's rather random, and not guaranteed to make it completely safe. Who knows what bits the sheep might be avoiding ... indeed the sheep may have a mentality towards self-preservation the shepherd isn't aware of. Maybe the grass above a land mine just isn't juicy and fresh enough to tempt a sheep.
Much better is to bring specialist mine hunters or engineers in to clear a path. They will need some expensive equipment like metal detectors to probe ahead, and when a mine is found, they need to work with an expert to remove and defuse it. But this is slow and methodical work, with everything almost grinding to a halt when a big problem is unearthed. In the story above, as your engineers clear a path, there will be someone who will complain it's too slow and the café will be closed by the time you're across the field.
And though you'll have cleared a path, it may still not be safe. Your friend needs to go to the toilet behind a bush whilst this is going on, but that involves stepping off the safe path. When can you declare a field safe and move on? Do you keep going backwards and forward with your engineers until you've covered every square inch? Do you cover the main footpaths first? Or can you claim it safe if you've not found any mines for the last couple of hours?
How can you ever really be sure? It's easy to know about the presence of mines - they have a way of making their presence known - but how can you be confident of their absence? How can you be sure that as you're unearthing mines in one part of the field, some scoundrel isn't laying new ones in the other end (ooh, and you thought the minefield was static - that could be a dangerous assumption)?
That question is of course one that applies to testers, managers, developers. How can you be sure you've de-mined your software of defects? Of course you never can be sure, but it doesn't hurt to have covered as much ground as possible. Every mine you find makes the field safer.
In reality we tend to bring in our specialist demolition engineers, our Testers to check methodically as many paths as possible. Then to cover ourselves, we bring in our users for acceptance, and send out the sheep ...
As with so much in life there's no "one way" to solve this problem scenario.
There's really no way to one way, no right way to solve this. You have a drive to get somewhere (your café). But you can easily spend the rest of your life going backwards and forwards in this field before you can declare it safe. Of course if you're careless, you will be spending the rest of your life here.
At the end of the day, the most important thing is we and everyone in our party respects that we're in a minefield, and act accordingly. Not letting our leaders persuade us "you're all being silly, it's just one mine, c'mon follow me, they'll be out of meringues if we dawdle ...".
WRITING 101: Why I love to write about testing ...
I have obviously written a lot about testing - I've over 200 articles here, a couple of books, and such an assortment of postings in various testing publications that I don't remember them all.
All of which might sound like a brag, but it isn't. Writing might seem to come easy to me, but it doesn't ... on my blog there are a lot of articles which are "in progress", but aren't ready. Sadly one of those is the upcoming article on test reporting, which I've spent several weeks on, but still aren't happy about the direction.
But this is an excellent time for me to talk a little about the writing process, and maybe encourage you to take it up a bit yourself.
In the heart wrenching movie Shadowlands, there is a line (amongst many very thought provoking moments from that movie) that I've always resonated with, "we read to know that we're not alone".
I have my own quote for writing, "we write to make sense of the world". To me, it's the heart of why I write - because I've got something to say. Often when I start, I'm not exactly sure what it is I've got to say, and it takes exploration to really discover what it is I want to say. And sometimes that surprises me.
Right now, on test reporting, I know that test reporting really links back to your "test exit criteria". They are a measure of "done" against your test exit criteria. It logically means that your test reporting can only be as good as your exit criteria. So guess what happens when you have shallow and lazy exit criteria?
Damn - that's thrown me, and rather than a simple article about test reporting, I now need to have a deeper think about what makes good exit criteria. But it doesn't disillusion me - not at all. It means I have to think deeper, and search harder through my personal experience.
But it also means that when I come on "the other side" of that article, I'll end up with a deeper understanding of the topics and the pitfalls. An understanding I hope I can take to my next project - onwards and upwards!
All of which might sound like a brag, but it isn't. Writing might seem to come easy to me, but it doesn't ... on my blog there are a lot of articles which are "in progress", but aren't ready. Sadly one of those is the upcoming article on test reporting, which I've spent several weeks on, but still aren't happy about the direction.
But this is an excellent time for me to talk a little about the writing process, and maybe encourage you to take it up a bit yourself.
In the heart wrenching movie Shadowlands, there is a line (amongst many very thought provoking moments from that movie) that I've always resonated with, "we read to know that we're not alone".
I have my own quote for writing, "we write to make sense of the world". To me, it's the heart of why I write - because I've got something to say. Often when I start, I'm not exactly sure what it is I've got to say, and it takes exploration to really discover what it is I want to say. And sometimes that surprises me.
Right now, on test reporting, I know that test reporting really links back to your "test exit criteria". They are a measure of "done" against your test exit criteria. It logically means that your test reporting can only be as good as your exit criteria. So guess what happens when you have shallow and lazy exit criteria?
Damn - that's thrown me, and rather than a simple article about test reporting, I now need to have a deeper think about what makes good exit criteria. But it doesn't disillusion me - not at all. It means I have to think deeper, and search harder through my personal experience.
But it also means that when I come on "the other side" of that article, I'll end up with a deeper understanding of the topics and the pitfalls. An understanding I hope I can take to my next project - onwards and upwards!
Subscribe to:
Posts (Atom)






