StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
358686
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-12-11T08:23:19.173
FavoriteCount
0
LastActivityDate
2008-12-11T08:23:19.173
LastEditDate
LastEditorUserId
0
OwnerUserId
9951
ParentId
292388
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
<p>I'd go the opposite of what have been said.</p> <h2>The client is your number one information source</h2> <ul> <li>Avoid intermediaries (human and technical)</li> <li>Keep tracks (not to use it against the customers, even if it can happen, but because he pays to get what he wants)</li> <li>Communicate - on your initiative - in a short regular basis but for small amount of times.</li> <li>Any doubt can be cleared asking the good questions. The guy don't want that ? Get rid of it (even if you like it better). The guy want that ? Why not, add time and money on the contract.</li> </ul> <h2>You must train your communication skills</h2> <p>Most of what has been said here before is essentially related to the fact that programmers usually have poor communications skills. So they fall into the typical traps :</p> <ul> <li>customers give them bad info</li> <li>they waste time</li> <li>they get stressed</li> </ul> <p>At the end, nobody is happy.</p> <p>But with trained communication skills you will learn to direct when, how long and about what your chats will be, and so :</p> <ul> <li>Make any deal quick and nice</li> <li>Give confidence to the client</li> <li>Understands what the client wants (not what he says he wants)</li> <li>Ensure is satisfied with the answer (even if it's nonsens for you)</li> </ul> <p>Everybody will be happier : the customer will feel good <strong>and let you work in peace</strong> while you will have the information to keep working. Eventually, the resulting software will be better.</p> <p>Think talking to customer is boring ? They think it too. And paperwork is boring as well, but you must do it, so do it well instead of looking for excuses.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBest practices for developers in dealing with clients
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USe-satis
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POBest practices for developers in dealing with clients
  singulars
  PostTypePostTypeId
  PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
3. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.