Dave Burke : Freelance .NET Web Developer specializing in Online Communities

How not to ask another developer for help

Most bloggers have had experiences like the one I had a minute ago:  Developers sending you an email for technical assistance on something you blogged about a long time ago.  They're humorous in hindsight but rarely at the time.  Sometimes these emails are thoughtful and articulate, but most often they are scribbled pleas dripping with expectation of a quick fix.  There are often language issues, too, and when I get one of those like this morning's email, I actually make more of an effort to help. I appreciate the attempt made.

I blogged about a SharePoint Web Services Authentication issue in June of 2004.  Here, here, and the solution, here.  The posts went into detail on the issues and the fix was pretty clear, but as is almost always the case the sender says "we've done [whatever] and it's still not working.  Any other ideas??"

This morning's email subject line was "same old not able to complete this action ISSUE" from tojo.

Mail from: Dave Burke
Sender: tojo
Email: removed@yahoo.co.in
IP Address: removed
--------------------------------------------------------------------------------
well he have tried all that options even the SOLVED one option still we have our friend popping on our screen.

2 dev servers, all properties are exactly identical, even ie settings, one is for intranet, other is for both intranet and internet users.
the error pops up only for the second one.
sites have been migrated from first one to the second one.
WE CANNOT EDIT properties of a column, but addition all works fine.
any clue why its happening



Okay WHAT action? WHAT issue?  I had to search my blog just to find what he was talking about, then recall the issue in my head before providing him with the basic solution that worked for me.  But the funny thing about this incident was that the email I sent him with the answer got bounced. Undeliverable Mail Returned to Sender.  Yahoo Mail Resources at yahoo.co.in were temporarily unavailable.  Maybe he'll get the reply eventually.

As I said, humorous in hindsight...


Comments (3) | Post RSS RSS comment feed

Posted on 2/17/2006 5:48:00 AM by Dave Burke
Categories: .NET
Tags: No tags for this post

Related posts

Comments

2/17/2006 9:58:02 AM Permalink

Dave,

I *SO* hear you on that. I get about 5 or so of those kinds of requests almost every day. Alot of weird ones that don't fully describe the problem and leave me not really sure what they are asking anyway.

I'll usually only reply to the ones that have fully thought out the problem, have done their research about the problem, and can clearly state that they need my help with (and aren't asking me to do it for them but to give them help in discovering the solution for them to run with).

-Ryan

Ryan Farley |

2/17/2006 10:12:55 AM Permalink

Father of Farley Five, thanks for empathizing.  Fortunately I don't get them very often, apparently much less than you do!  This one made a good lesson on what not to do, and when I received that bounced email I had to write about it. Smile

I figure if I can't get the answer on Google, I'll keep banging my head on the problem for several hours.  If I don't have the solution by then, I'm obviously missing something or will come back to it fresh another day.  I'm not calling the guys who ask those questions lazy or anything, but I think a lot of developers don't know how to find answers.  Another thing is that good developers are like dogs who won't let go of that bone until they know they've picked it clean.  Persistence on figuring out problems is a big part of being a developer in my experience.

That said, it's also part of maturing as a developer to know when to let something go and come back to it later.

Speaking of being a developer, I better get back to it.  No problem analysis today (that was yesterday.)  Today's just mindless coding...

Take care of the FF.

daveburke |

2/17/2006 10:39:22 AM Permalink

testing WH4L SMTP

daveburke |

Comments are closed

This site was built with the Sueetie .NET Open Source Community Framework. Learn more about Sueetie at Sueetie.com.