Telling the Story of An Application
Getting your client to communicate with you
Issue: 10.1 (November/December 2011)
Article Description: No description available.
Article Length (in bytes): 4,892
Starting Page Number: 77
RBD Number: 10010
Resource File(s): None
Related Link(s): None
Known Limitations: None
Excerpt of article text...
People often accuse developers of being nerdy and not having good communication skills. While that might be true in many instances, it has been my experience that many people looking to hire a developer are worse. It's not that they can't communicate it's just that they don't know how to tell the story of their application and it's up to you to help write it for them.
Let's face it, most people looking for a developer are not very technical themselves. If they were, they would probably be attempting to code their project themselves. So they start with several strikes against them. They don't know the lingo that we use. They may not be very computer literate in general, but they've got this great idea. You ask them to write a story about their application with as many details as possible and send it to you.
And you get two paragraphs.
I can hear some of you laughing because you know this happens all too often. Their two paragraphs could describe any application in the world or it's a work of fiction. They're thinking accounting application and their story sounds like a third-person shooter game. Okay, that might be a bit of an exaggeration, but it's certainly not uncommon to have a huge disconnect between what they say and what they give to you in writing.
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.