<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="0.92" xml:base="http://www.testingreflections.com">
<channel>
 <title>David Gilbert's blog</title>
 <link>http://www.testingreflections.com/blog/776</link>
 <description></description>
 <language>en</language>
<item>
 <title>Heuristication</title>
 <link>http://www.testingreflections.com/node/view/4172</link>
 <description>Good morning, class.  Today, we are going to learn a new word – Heuristication.  Heuristication is a state of sophistication in dealing with and applying Heuristics as an element in an overall test methodology.&lt;br /&gt;
&lt;br /&gt;
What does Heuristication look like?  How can you identify it?  Well, in order to answer those questions, first we have to understand what heuristics themselves are.&lt;br /&gt;
&lt;br /&gt;
A heuristic is a fallible method for solving a problem.  “Fallible?”, you may ask, “Why would I want to use something that’s fallible?”  Well, lets look at a slightly different wording of that same idea…a heuristic is a general rule of thumb that works most of the time.  Now we can begin to see the value.  It is general, and works most of the time, so it can provide a solution quickly, without thinking very hard or very long about it.</description>
<pubDate>Wed, 20 Sep 2006 10:51:42 -0500</pubDate></item>
<item>
 <title>The Gilbertian Squirrel Dodge</title>
 <link>http://www.testingreflections.com/node/view/4167</link>
 <description>Another chapter in the continuing saga of my personal quest for good heuristics.&lt;br /&gt;
&lt;br /&gt;
Earlier this summer, I had the honor of attending WHET, the Workshop on Heuristic and Exploratory Techniques.  Leaving the workshop one afternoon, lost in deep thought over the day’s events, I was strolling down the sidewalk toward my car.  In the grassy area off to my left, I was vaguely aware of some squirrels playing away.  As I approached, they stood up and froze, suddenly leery of the giant monster who had just invaded their space.  As I continued to walk along the sidewalk, at complete right angles to the squirrels, staring at the ground in front of me lost in thought, taking no notice of them whatsoever, one of them finally could not take the pressure any longer, and he bolted…unfortunately, he chose his escape route very poorly, and before I realized what he was doing, the poor little guy ran headfirst, full speed, directly into the side of my foot.  Right into my foot!!  I’m not kidding…he hit me so hard it hurt.  He bounced off of my foot, rolled over, jumped up and picked a new direction to run.  I was amazed.</description>
<pubDate>Fri, 15 Sep 2006 13:34:24 -0500</pubDate></item>
<item>
 <title>Eat Da Dog!</title>
 <link>http://www.testingreflections.com/node/view/4164</link>
 <description>Over the past few weeks, I have been working with James Bach on my BCRIT certification.  Through that process, I have identified my use of heuristics as a good area for potential growth, and so I try to spend some time each day actively thinking about this.  For those not familiar, a heuristic is a key word or phrase that encapsulates some larger idea, and triggers you to apply some strategy or behavior in your testing.  You try to pick heuristics that will be easy for you to remember, something personal or interesting.  Something amusing is always a good choice, James’ “Dead Bee” heuristic being a good example.</description>
<pubDate>Thu, 14 Sep 2006 08:45:44 -0500</pubDate></item>
<item>
 <title>Predicting the Path of the Storm</title>
 <link>http://www.testingreflections.com/node/view/3873</link>
 <description>Recently, three unrelated events have given birth to a new idea in my head, and I wanted to share it with you.  So, to properly set up the background, the three unrelated events:&lt;br /&gt;
&lt;br /&gt;
At the recent CAST, James Bach presented a keynote, “&lt;a href="http://www.associationforsoftwaretesting.org/conference/keynote.html#"&gt;Against Certification&lt;/a&gt;”.  During that presentation, one of the things he did was to review some of the “Body of Knowledge” documentation upon which such certifications were based.  As he reviewed this documentation, one of the things I was struck by was an underlying pattern of motive driving much of the documentation.  That motive was the ability to predict, manage, and control the SDLC.  Much of this “Body of Knowledge” for test certification was obviously written by managers, not testers.</description>
<pubDate>Tue, 27 Jun 2006 12:11:11 -0500</pubDate></item>
<item>
 <title>A Month of Gatherings</title>
 <link>http://www.testingreflections.com/node/view/3829</link>
 <description>I have just finally landed after spending a month running around to various conferences and workshops.  I will discuss each of them in a bit of detail below, but first I want to talk about the entire experience.&lt;br /&gt;
&lt;br /&gt;
Conferences, tradeshows, and workshops have many purposes.  For vendors, it is an opportunity to try and get your wares in front of an interested audience.  For practitioners, it is an opportunity to see the latest in tools and technology, and attend tutorials and sessions, sometimes from prominent industry leaders.  And for everyone, it is an opportunity to meet new colleagues,  reconnect with old friends, and engage in that most basic and valuable activity of any true conference…conversation.</description>
<pubDate>Tue, 13 Jun 2006 23:08:47 -0500</pubDate></item>
</channel>
</rss>
