Exploration Through Example

Example-driven development, Agile testing, context-driven testing, Agile programming, Ruby, and other things of interest to Brian Marick
191.8 167.2 186.2 183.6 184.0 183.2 184.6

Tue, 03 Feb 2004

Investigative Journalist

[Update: corrected misspelling]

Dave Liebreich talks about people who are not business experts interviewing people who are. He uses investigative journalism as a model. What struck me most was this:

The interviewee *believes* the interviewer has a perspective different from their own, or has an incomplete understanding of some of the areas.

That strikes a chord with me, as I'm interested not just in person X's job, or in person Y's job, but in how they think about each other's job, and in how they attempt to structure their interactions with respect to those thoughts. I'm interesting in what's between roles. That accounts for my interest in boundary objects and in some of the literature on "marginal" or "liminal" people - those who live on the boundaries between cultures and cross-pollinate them. (The Constant Reader will guess that I fancy myself one of those people.)

In another entry, Dave writes:

But I still run scripts with tracing turned on, every now and then, just to get a feel for the rhythm of the system and maybe discover something that is off a beat or two.

Part of what I conceive of as the promise of the Agile methods is that they will help make phrases like "the rhythm of the system" or "what the code is trying to tell us" not seem wacko. They're a groping way of expressing something that has real consequences.

## Posted at 07:11 in category /misc [permalink] [top]

About Brian Marick
I consult mainly on Agile software development, with a special focus on how testing fits in.

Contact me here: marick@exampler.com.




Agile Testing Directions
Tests and examples
Technology-facing programmer support
Business-facing team support
Business-facing product critiques
Technology-facing product critiques
Testers on agile projects

Permalink to this list


Working your way out of the automated GUI testing tarpit
  1. Three ways of writing the same test
  2. A test should deduce its setup path
  3. Convert the suite one failure at a time
  4. You should be able to get to any page in one step
  5. Extract fast tests about single pages
  6. Link checking without clicking on links
  7. Workflow tests remain GUI tests
Permalink to this list


Design-Driven Test-Driven Design
Creating a test
Making it (barely) run
Views and presenters appear
Hooking up the real GUI


Popular Articles
A roadmap for testing on an agile project: When consulting on testing in Agile projects, I like to call this plan "what I'm biased toward."

Tacit knowledge: Experts often have no theory of their work. They simply perform skillfully.

Process and personality: Every article on methodology implicitly begins "Let's talk about me."


Related Weblogs

Wayne Allen
James Bach
Laurent Bossavit
William Caputo
Mike Clark
Rachel Davies
Esther Derby
Michael Feathers
Developer Testing
Chad Fowler
Martin Fowler
Alan Francis
Elisabeth Hendrickson
Grig Gheorghiu
Andy Hunt
Ben Hyde
Ron Jeffries
Jonathan Kohl
Dave Liebreich
Jeff Patton
Bret Pettichord
Hiring Johanna Rothman
Managing Johanna Rothman
Kevin Rutherford
Christian Sepulveda
James Shore
Jeff Sutherland
Pragmatic Dave Thomas
Glenn Vanderburg
Greg Vaughn
Eugene Wallingford
Jim Weirich


Where to Find Me

Software Practice Advancement


All of 2006
All of 2005
All of 2004
All of 2003



Agile Alliance Logo