|
Do you do most of your dealings with the client face to face or are you more phone and email?
|
|
|
|
|
Me, I am more face to face.
|
|
|
|
|
I have managers between me and the users 
|
|
|
|
|
That is the only way that works.
I'd rather be phishing!
|
|
|
|
|
I'll do face to face for major / new (and starting of course)
followed by written version - proper document (not just email - formatting lost etc.)
not a big fan of phone, if so always followed up with email (if they don't I will)
- again if it's big / significantly new I insist on face to face - can whiteboard etc
small items prefer email
I'm a stickler for "ensure it's written down" - even if trivial, just so it's recorded.
Message Signature
(Click to edit ->)
|
|
|
|
|
I have a support team between me and clients... On those occasions I have to comunicate with them it is done by phone or personally almost equally, however everything is written in emails later...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
If it's the start of a project then face to face.
If it's a major or monthly update and I'm in a senior role then usually video conference.
If it's a major or monthly update and I'm not in a senior role then I'm usually not involved.
Day to day stuff via email, very rarely use the phone for anything, it's much better to have unambiguous communications and a paper trail
If the client company has hot women then face to face. Always face to face.
|
|
|
|
|
All of my "clients" are in-house and we use a mix of phone and e-mail, depending on the urgency of the issue. I work for a very large, privately-held company and all of my work is for internal use.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Mostly via a support team so I never have to meet the actual clients. All clients for all projects are in-house (I work for a county government) so I rarely meet clients - although I have for some smaller projects.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
That depends, how far away is the client, how much needs to be discussed, how important is the discussion, how well does the client pay...
I prefer face to face, but I prefer not spending hours in traffic even more 
|
|
|
|
|
For me it's almost always phone/email/remote desktop.
I handle frontline support for the software I develop and 'rent/lease' to clients around the US. Over 20 years this now includes 2 major desktop apps, the 100 or so add-on modules/utilities that support them, and around 2 dozen web applications.
Devs dealing directly with the clients may be uncommon, but I believe it has benefits for both parties.
0: The developer gets to practice their people skills.
1: The client gets a direct line to the person who can most likely fix/improve something.
2: The developer sometimes gains domain knowledge.
3: Products improve quickly to eliminate those annoying client phone calls.
Regarding #3, this has been the biggest driver for me...to lessen the length of time I need to be on a call/remote to find and fix a problem. To this end, our main products have some really nice support features for submitting and receiving files for troubleshooting/fixing problems:
a: downsize/zip/upload feature for our managed sql server users to instantly post a customer database. The downsized file is in Access format. Our apps are agnostic (for the most part) so it's possible to stay online with a client while I download and hookup to his current database to find a problem.
b: download/run script files. The main apps also have the ability to download and run script files for anything from automating imports, to fixing a specific problem, to pre-configuring a new module.
c: easy to use updaters.
Having an automated deployment chain here is essential. It has occurred when an issue has been debugged, fixed, recompiled, and redeployed, (signed/sealed/delivered), and downloaded in < 10 minutes without leaving the remote. Stupid mistakes happen, but are dealt with swiftly!
"Go forth into the source" - Neal Morse
|
|
|
|
|
 that's an outstanding reply, and I congratulate you on your implementation. if only a mere mortal, like me, could create such an update facility !
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
Thank you for the kind words!
BillWoodruff wrote: if only a mere mortal, like me, could create such an update facility
Don't underestimate your abilities...it's just moving bits! Seriously though, if you need ideas, I'd be happy to help.
"Go forth into the source" - Neal Morse
|
|
|
|
|
I try to maximize the time spent with the client's credit cards.
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
At my last job I just had managers making design decisions in-perpetuity.
There were no clients.
Manager: If we build it, clients will come.
Me: What exactly are we building?
Manager: Whatever the clients want.
Me: What clients?
Manager: The ones we'll get after you're done building it.
Me: Build what exactly?
Manager: Whatever the clients want, we've been over this already.
Meanwhile, whatever we were building was already getting a price tag of 15k a piece.
|
|
|
|
|
One client in town where I live, Face to face.
The others, phone and email.
Technology is wonderful, WHEN IT WORKS.
|
|
|
|
|
Had another discussion about it, and the question materialized:
Would you as a developer sit/use in a self driving car?
And under what circumstances/limitations?
|
|
|
|
|
|
Give it another twenty years.
|
|
|
|
|
Nope.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
I'd be OK with it as long as there was a big red button.
Message Signature
(Click to edit ->)
|
|
|
|
|
|
It would we be an awful lot safer than one driven by me!
And I think that's also true of one driven by many others. Let's face it, there are an awful lot of humans who should never be allowed behind a wheel.
Sure, the tech's in it's infancy at the moment but I'd be very surprised to see vehicles entrusted to human operators thirty years from now.
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
I went to Nvidia's GTC (GPU Trade Conference) this past March and self-driving cars were HUGE there. Several companies were exhibiting their work and Nvidia was also. They had their self-driving truck test bed there and were showing videos of it in action. The video was from a camera just above and behind the driver and it showed him and a passenger both just sitting there with their hands in their laps as the truck drove down the highway, observing traffic signals, exiting the road and re-entering. It was rather fascinating.
The bottom line is lots of companies and people are working on them. I would be interested in riding in one.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
