My Secret Life as a Spaghetti Coder
home | about | contact | privacy statement
A couple of weeks ago, John Roth posted a link to Martin Fowler's article on Customer Affinity on the XP yahoo groups list.

I just like being reminded that we shouldn't be thinking "those awful customers want something else done now! Can you believe it?" I think we have those thoughts far too often. I know I used to.

I used to be the type who would actively try to avoid conversations with the customer - get some manager to do it. I've since stopped that approach, but every once in a while I find myself thinking "well that's a stupid idea." In the past, I'd either just do it to get it over with, or tell someone else to tell the customer it was a stupid idea (in more diplomatic terms, of course).

Now, I find it much more helpful and rewarding to discuss (without the use of a proxy) the objectives they are trying to reach with the "stupid idea." I've found a lot of times, the ideas aren't that stupid. Other times, I can suggest a different approach that would solve the problem in a more meaningful way. Still others, I've talked myself out of good paying work that didn't need to be done because of an unfounded fear of a potential problem.

I don't think you can develop good software without understanding the goals of the customer for whom you are writing it. And how can you understand the goals without having that "customer affinity?"

It's a pity so many waste so much time developing software that is essentially useless. I always smile when I hear the "go get this done and come back in 6 months with the finished product" stories. That used to be me, and I mostly always came back with the wrong product.

I like my newer approach much better, and I like to be reminded from time to time about it. That's what this article did for me, and it's definitely worth a read.

Hey! Why don't you make your life easier and subscribe to the full post or short blurb RSS feed? I'm so confident you'll love my smelly pasta plate wisdom that I'm offering a no-strings-attached, lifetime money back guarantee!

Leave a comment

There are no comments for this entry yet.

Leave a comment

Leave this field empty
Your Name
Email (not displayed, more info?)


Subcribe to this comment thread
Remember my details

Picture of me

.NET (19)
AI/Machine Learning (14)
Answers To 100 Interview Questions (10)
Bioinformatics (2)
Business (1)
C and Cplusplus (6)
cfrails (22)
ColdFusion (78)
Customer Relations (15)
Databases (3)
DRY (18)
DSLs (11)
Future Tech (5)
Games (5)
Groovy/Grails (8)
Hardware (1)
IDEs (9)
Java (38)
JavaScript (4)
Linux (2)
Lisp (1)
Mac OS (4)
Management (15)
MediaServerX (1)
Miscellany (76)
OOAD (37)
Productivity (11)
Programming (168)
Programming Quotables (9)
Rails (31)
Ruby (67)
Save Your Job (58)
scriptaGulous (4)
Software Development Process (23)
TDD (41)
TDDing xorblog (6)
Tools (5)
Web Development (8)
Windows (1)
With (1)
YAGNI (10)

Agile Manifesto & Principles
Principles Of OOD
Ruby on Rails

RSS 2.0: Full Post | Short Blurb
Subscribe by email:

Delivered by FeedBurner