Dorothea Salo discusses the cult of the programmer, an insular world where programmers never ever ever talk to the people who are supposed to use their programs before they create them. She comes to the remarkable insight that if you talk to the users, you wind up with better software.
<sigh> Usability people have been screaming about this for years. There are entire professions dedicated to studying users and communicating with them to help programmers create better software. Ethnographers and anthropologists have found new uses for their esoteric fields in corporate settings, sussing out the needs of users. Techniques such as contextual inquiry allow development teams to glean insights into the way users use their tools before programmers start programming. Usability tests help refocus efforts once programming has started by checking to see if the assumptions programmers have baked into their programs match the situation on the ground.
I don't mean to rag on Dorothea, but given all the ink expended on usability in recent years, I'm surprised she's not aware of all this. I know usability is a dirty word with a lot of people, but there are facets of the profession that really do provide a decent response to the problem Dorothea points out. Sadly, it's a response more often honored in the breach than the practice, often brought into the development process at the last minute to sprinkle usability dust over a product that's already pretty well fixed in form if it's used at all, rather than being involved from the beginning in shaping the direction of development.
Posted at 1:28 PM
I guess I'm just dense, because I didn't quite understand from your original posting that you wanted the programmers to actually *do* the jobs. While I don't doubt that that would be an improvement to the situation you describe, I think the understanding gained by doing that would be pretty superficial. The insights that can be gained by doing a job for a few hours are quite different from the insights that can be gained by doing a job for a few years, and those insights are the kind best teased out by the techniques I mentioned. So I think it would probably be a useful exercise, but probably not as useful as the techniques used by usability professionals.
Posted by ralph at 6:12 PM, March 30, 2003 [Link]
"D responded quickly to my little nudgeback earlier. And she's sticking by her guns: But, dang it, this time I am not wrong. Good on you, Dorothea. I like people who stand their ground. I rarely do so it's very refreshing for me to see it in others. However, I have to respectfully disagree with your assessment that software can only be created by people who've done the work -- walked the walk, so to speak. In some ways..., well, okay in some twisted ways, that's the same as saying I can't really understand what happens in the massage parlour business just from the explicit requirements given me by the Madame. Good, well trained programmer/analysts are expert in interviewing clients and putting their words into requirements that other developers can follow. Now, after you work in an industry for a while you pick up the talk. I've worked in manufacturing so I understand workorder, Bill-Of-Materials, supply chain and run. I have a good idea what a manufacturing application will need. But I never needed to run the line to get this understanding. It was a question of meeting with the folks who are expert and knowing how to maximize their"
Tracked: March 30, 2003 09:29 PM
Please note: your e-mail address is required, but will not be posted on the site. I reserve the right to delete any inappropriate posts.
This site is copyright © 2002-2008, Ralph Brandi.
I do know, actually. But there's a difference between studying a job and *doing* it.
I think programmers ought to get out there and *do* jobs, not just study them. And that's the difference I was gunning for in my post.
I don't doubt the techniques you mention are good proxies. But proxies only get you so far.
Nobody's tried direct experience, that I know of. Wish somebody would, is all.
Posted by Dorothea Salo at 2:02 PM, March 30, 2003 [Link]