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, 27 Mar 2007

An open letter on open letters

I'm in England, jetlagged. Some person from the States just called my cell phone / alarm clock with a wrong number at 3:00 a.m. local time, and I can't get back to sleep. I am therefore going to do something I will regret in the clear light of morning.

The Agile Alliance recently published its position on certification. I wrote it. I was told last evening, and I believe it, that people have been interpreting it to have the message "you better get certified if you want a job in Agile." I have long maintained, as a matter of both principle and practice, that a misunderstood message is the fault of its sender. But Jeez Louise, the letter is pretty explicit:

... We also believe that employers should not require certification of employees.

... there are many skilled practitioners who are not certified. Excluding them from consideration would be a poor business decision.

The last few years have smacked me in the face with that kind of thing over and over. People are so apt to jump to conclusions, to assume that any unknown motive must be a bad one, to focus on pointing out weakness to the exclusion of helping shore up strengths. Trying to accomplish something positive is just too damn much frustration not to get paid for it. I say it's spinach, and I say to hell with it.

## Posted at 20:29 in category /junk [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