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

Sun, 28 Aug 2005

Hints instead of rules

Via John D. Mitchell, an interesting article about a minimalist reaction to the tunnel vision rules promote:

Hans Monderman is a traffic engineer who hates traffic signs. Oh, he can put up with the well-placed speed limit placard or a dangerous curve warning on a major highway, but Monderman considers most signs to be not only annoying but downright dangerous. To him, they are an admission of failure, a sign - literally - that a road designer somewhere hasn't done his job. "The trouble with traffic engineers is that when there's a problem with a road, they always try to add something," Monderman says. "To my mind, it's much better to remove things."

Monderman is one of the leaders of a new breed of traffic engineer - equal parts urban designer, social scientist, civil engineer, and psychologist. The approach is radically counterintuitive: Build roads that seem dangerous, and they'll be safer.

Update: In response, Randy Mcdonald writes:

Build roads that seem dangerous, and they'll be safer.

was a principle that I first encountered when I read that Kowloon Airport in Hong Kong (I think that is its name, ICBW) had a remarkable safety record, given that the landing process was very terrifying. Ever since I read that, I use the term I put in my subject line [The Kowloon Airport Syndrome] for such situations.

Having flown into the old Hong Kong airport, that strikes a chord with me.

It occurs to me that I want to take the idea beyond safety. What I want to remember from the article is how physical space can be engineered to cause people to attend to what's easily ignored. What they might not see "in a state of nature" can be made visible. Ditto for those things that rules divert attention from (because following the rules is supposed to eliminate the need for attention).

Consider our friend the big visible chart. They are supposed to fall in that middle ground - not rules, but still acting to nudge people. Sometimes they don't work. Why not? Ditto for standup meetings, bullpens, etc. How can they be better engineered?

## Posted at 08:55 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.

 

Syndication

 

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

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

 

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

 

Join!

Agile Alliance Logo