James Bach responded to my recent post, Are You Following the Instructions on the Paint Can?, with Studying Jeff Atwood's Paint Can.
Being under Bach's intensive analytical microscope feels a lot like an interview with Hannibal Lecter. It's flattering, but it's also a little scary. You learn a tremendous number of things about yourself – at the risk of your professional dignity, and maybe even your soul.
In a previous entry, I complained about the fact that Bach's blog doesn't allow comments. Some readers took this as a personal attack on James. Nothing could be further from the truth. I've been meaning to write about that topic for months, and James' blog just happened to be the most recent case. I have tremendous respect for Bach and the way he aggressively questions convention. Prior to this paint can dialog, I had already based two blog entries on his writing: It's Better Than Nothing and Best Practices and Puffer Fish. If anything, we should form a mutual admiration society.
Now that I've gotten all the disclaimers out of the way, I can respond to the actual content of Mr. Bach's entry. First, I want to give James credit for identifying a key assumption:
"What I find particularly interesting is that none of the mistakes on this checklist have anything to do with my skill as a painter."I think what Jeff meant to say [here] is that they have nothing to do with what he recognizes as his skill as a painter. I would recognize these mistakes, assuming for the moment that they are mistakes, as being strongly related to his painting skill. Perhaps since I don't have any painting skill, it's easier for me to see it than for him. Or maybe he means something different by the idea of skill than I do. (I think skill is an improvable ability to do something) Either way, there's nothing slam dunk obvious about his point. I don't see how it can be just a matter of "read the instructions stupid."
This is dead on. I used to run a painting business in college. So my idea of "painting skill" – for the record, it's how cleanly and evenly you physically apply a coat of paint to the surface – is quite different than James'. If you read any of his writing, you'll quickly determine Mr. Bach is incredibly effective at sussing out all the assumptions you're making that you don't realize you're making. And questioning assumptions is a tremendously powerful method of investigation, particularly when someone helps you identify the ones that you're blind to.
Beyond that, the general thrust of Bach's reply is that instructions aren't always helpful:
Consider all the instructions you encounter and do not read. Consider the software you install without reading the "quickstart" guide. Consider the clickwrap licenses you don't read, or the rental cars you drive without ever consulting the drivers manual in states where you have not studied the local driving laws. Consider the doors marked push that you pull upon. Consider the shampoo bottle that says "wash, rinse, repeat." Well, I have news for the people who make Prell: I don't repeat. Did you hear me? I don't repeat.I would have to say that most instructions I come across are unimportant and some are harmful. Most instructions I get about software development process, I would say, would be harmful if I believed them and followed them. Most software process instructions I encounter are fairy tales, both in the sense of being made up and in the sense of being cartoonish. Some things that look like instructions, such as "do not try this at home" or "take out the safety card and follow along," are not properly instructions at all, they are really just ritual phrases uttered to dispel the evil spirits of legal liability. Other things that really are instructions are too vague to follow, such as "use common sense" or "be creative" or "follow the instructions."
There are, of course, instructions I could cite that have been helpful to me. I saw a sign over a copy room that said "Do not use three hole paper in this copy machine... unless you want it to jam." and one next to it that said "Do not use the Microwave oven while making copies... unless you want the fuse to blow." I often find instructions useful when putting furniture together; and I find signs at airports generally useful, even though I have occasionally been steered wrong.
Instructions can be useful, or useless, or something in between. Therefore, I propose that we each develop a skill: the skill of knowing when, where, why and how to follow instructions in specific contexts. Also, let's develop the skill of giving instructions.
Although I absolutely agree that you must be critical of everything you read, James' statement that "instructions can be useful, useless, or something in between" is just as unhelpful as my "for best results, follow the instructions" advice. I implicitly assumed that the person reading the instructions on the paint can was smart enough to read those instructions as suggestions, reminders, and guidelines – not as a recipe to be slavishly followed to the letter.
I agree with Bach's assertion that a paint can is neither a supervisor, nor a mentor, nor a judge of quality. A static list of instructions is no substitute for hands-on help with your painting project from someone who has extensive painting experience.
But you rarely have the luxury of working with experts. Most of the time, you're on your own, and the bulleted list is all you have. Consider this list of painting tips from John Montgomery. We had a problem a few days ago while painting. Our latex paint was drying exceptionally fast on the second coat and causing problems with the smoothness of the finish. Because I had read John's painting tips, I remembered this bullet point from his list:
Mix your paint and add Flotrol. If you're more than 24 hours from the paint store, open your paint and mix it. You should also add Flotrol (latex) or Penetrol (oil) to it – these paint conditioners don't thin the paint or change its color, but they do affect how smoothly it goes on and limit brush and roller stroke evidence.
I went to the store, bought some Flotrol, mixed it in, and our problem was solved.
It's doubtful I would have been able to fix this problem if I hadn't followed at least some of the instructions on John's blog. Although I agree with James Bach's central point – you should question everything you read – I sort of assumed everyone does this already. Maybe I assume too much. But sometimes a bulleted list of instructions sure does come in handy.
I like these reads - James is definitely someone you don't want to tangle with and I admire what you're saying here. I read both posts (can't believe i made it) and in reading his, it reminded me of a good friend (Harvard/Berekely grad with a PhD) who is insanely intelligent. If he chose to, he could take whatever side of an argument he wanted, dive into the minutae (or ride on top of it), and prove you wrong. Seems to me that's what's happening here.
I think you're both right. Your point - there is a base level of intelligence that can be assumed - is dead on. If we didn't have it, we would be in the trees eating our own poop. His point - instructions can be meaningless - is also dead on. The legalese one is the most illustrative of that.
I live in Hawaii and surf whenever I can. I find that the act of riding a wave is analogous to ... well just about everything. It's a dynamic environment full of all sorts of movement that you need to interpret and work with as you go. You could follow instructions from Kahuna and it will get you to a certain point (like paddling out and maybe standing up), but being a "skilled" surfer... well let's just it takes time and the journey is long, and really only YOU know when you have this skill.
So my point is this - our industry is an ocean of opinions with waves of ideology and fads. Your "skill" only matters in what your client perceives as your value. Your ability to change, adjust, readjust, know when to "be manageable" and follow instructions and when to kick them to the curb - all of these things define your "skill".
I appreciate both of your articles - made me think about a lot of things. Especially the 5-7 North that's due in today. Gotta head out!
Aloha!
Rob Conery on May 3, 2006 5:16 AMIt would be a mistake to assume that James' attacks on best practices are mere sophistry. "Best pratice" thinking (or rather, the absence of thinking about practices) is a serious problem in our profession.
Michael Bolton
Michael Bolton on May 3, 2006 10:17 AMAll this talking about paint reminds me: Must read Paul Graham's latest essay.
Zvika Rap on May 4, 2006 2:44 AMPersonally, the main value I get from instructions comes in times and contexts where I don't want to invest the time or energy into becoming an expert on something. One example, if you'll forgive the descent into coding, is the use of StringBuilder in tight loops. I tell the developers that work for me to always use StringBuilder in cases where they are doing string addition in loops. Does this advice always lead to the most efficient code? Not so much. On the other hand, it makes sure that they never do the really dangerous things that might lead to death and destruction!
gerrard on May 4, 2006 4:57 AMMust read Paul Graham's latest essay.
It took me waaaay too long to figure this out: hackers and painters. ;) Graham does have a new essay up, btw, and it's excellent as usual.
http://www.paulgraham.com/startuplessons.html
Jeff Atwood on May 4, 2006 5:07 AMVery interesting topic. Lot's of these areas are addressed in Gary Klein's book "Sources of Power: How People Make Decisions". Despite the kooky title, it's the book I had hoped Blink would be.
One sections has "considerations in communicating intent" which are all relevant in providing useful instructions.
1. The purpose of the task (the higher-level goals).
2. The objective of the task (an image of the desired outcome).
3. The sequence of steps in the plan.
4. The rationale for the plan.
5. The key decisions that may have to be made.
6. Antigoals (unwanted outcomes).
7. Constraints and other considerations.
One might consider these aspects of the usability for a set of instructions.
Jeez - I don't have enough time in the day to read the stuff I'm actually interested in. Now I have to read about house painting and actually remember something about it?
No thanks. I think I'll just continue to ignore my crappy paint jobs. I mean - it's not really for looks; the paint's really there to hold things together, right?
Flotrol Natural Bladder Control
http://karmictours.com/flotrol
I like this page particularly because I'm a
painting contractors in west palm beach
Anactorres32 on September 7, 2010 3:00 PMThe comments to this entry are closed.
|
|
Traffic Stats |