Wednesday, February 25, 2009

[MW:1628] Before You Ask

Dear all

It doesn’t matter which type of question it is ….

We all like answering questions for people who have demonstrated they can learn from the answers.

Before You Ask

Prepare your question. Think it through. Hasty-sounding questions get hasty answers or none at all. The more you do to demonstrate that having put thought and effort into solving your problem before seeking help, the more likely you are to actually get help.

Never assume you are entitled to an answer. You are not; you aren't, after all, paying for the service. You will earn an answer, if you earn it, by asking a substantial, interesting, and thought-provoking question — one that implicitly contributes to the experience of the community rather than merely passively demanding knowledge from others.

Use meaningful, specific subject headers

The subject header is your golden opportunity to attract qualified experts' attention in around 50 characters or fewer. Don't waste it on babble like "Please help me" (let alone "PLEASE HELP ME!!!!" messages with subjects like that get discarded by reflex). Don't try to impress us with the depth of your anguish; use the space for a super-concise problem description instead.

Looser:

HELP! Need welding procedure!

Smart:

How to weld overlay a Duplex SS?

Smarter:

UNS31803 weld overlay on A105, What are the essential parameters?

If you ask a question in a reply, be sure to change the subject line to indicate that you're asking a question. A Subject line that looks like "Re: or "Fw:  is less likely to attract useful amounts of attention.

Do not simply hit reply to a list message in order to start an entirely new thread. This will limit your audience.

Changing the subject is not sufficient. Me, and probably other mail readers, looks at other information in the e-mail's headers to assign it to a thread, not the subject line. Instead start an entirely new e-mail.

Write in clear, grammatical, correctly-spelled language

Expressing your question clearly and well is important. If you can't be bothered to do that, we can't be bothered to pay attention. Spend the extra effort to polish your language. It doesn't have to be stiff or formal — in fact, hacker culture values informal, slangy and humorous language used with precision. But it has to be precise; there has to be some indication that you're thinking and paying attention.

Spell, punctuate, and capitalize correctly. Don't confuse "its" with "it's", "loose" with "lose", or "discrete" with "discreet". Don't TYPE IN ALL CAPS; this is read as shouting and considered rude. (All-smalls is only slightly less annoying, as it's difficult to read.)

Be precise and informative about your problem

·         Describe the symptoms of your problem carefully and clearly.

·         Describe the research you did to try and understand the problem before you asked the question.

·         Describe the diagnostic steps you took to try and pin down the problem yourself before you asked the question.

Describe your problem's symptoms in chronological order

Don't flag your question as "Urgent", even if it is for you

That's your problem, not ours. Claiming urgency is very likely to be counter-productive: most will simply delete such messages as rude and selfish attempts to elicit immediate and special attention.

If you find this mysterious, re-read the rest of this how-to repeatedly until you understand it before posting anything at all.

Courtesy never hurts, and sometimes helps

Be courteous. Use "Please" and "Thanks for your attention" or "Thanks for your consideration". Make it clear you appreciate the time people spend helping you for free. Politeness does increase your chances of getting a useful answer.

Follow up with a brief note on the solution (The Most Important)

Send a note after the problem has been solved to all who helped you; let them know how it came out and thank them again for their help. If the problem attracted general interest, it's appropriate to post the follow-up here.

Consider how you might be able to prevent others from having the same problem in the future. Ask yourself if a documentation or FAQ would help, and if the answer is yes send that to the group.

This sort of good follow-up behavior is actually more important than conventional politeness. It's how you get a reputation for playing well with others, which can be a very valuable asset.

How to Interpret Answers

If you don't understand...

If you don't understand the answer, do not immediately bounce back a demand for clarification. Use the same tools that you used to try and answer your original question (Books, FAQs, the Web, skilled friends) to understand the answer. Then, if you still need to ask for clarification, exhibit what you have learned.

If You Can't Get an Answer

If you can't get an answer, please don't take it personally that we don't feel we can help you. Sometimes the members of the asked group may simply not know the answer. No response is not the same as being ignored, though admittedly it's hard to spot the difference from outside.

In general, simply re-posting your question is a bad idea. This will be seen as pointlessly annoying. Have patience: the person with your answer may be in a different time-zone and asleep. Or it may be that your question wasn't well-formed to begin with.

How to Answer Questions in a Helpful Way

Be gentle. Problem-related stress can make people seem rude even when they're not.

Reply to a first offender off-line. There is no need of public humiliation for someone who may have made an honest mistake. A real newbie may not know how to search archives or where the FAQ is stored or posted.

If you don't know for sure, say so! A wrong but authoritative-sounding answer is worse than none at all. Don't point anyone down a wrong path simply because it's fun to sound like an expert. Be humble and honest;

If you can't help, don't hinder. Don't make jokes about procedures that could trash the user's item — the poor chap might interpret these as instructions.

Ask probing questions to elicit more details. If you're good at this, he/she will learn something — and so might you. Try to turn the bad question into a good one; remember we were all newbie’s once.

Help your community learn from the question.

If you did research to answer the question, demonstrate your skills rather than writing as though you pulled the answer out of your butt. Answering one good question is like feeding a hungry person one meal, but teaching them research skills by example is teaching them to grow food for a lifetime.

 

Thank you all and more suggestions are welcome

 


From: materials-welding@googlegroups.com [mailto:materials-welding@googlegroups.com] On Behalf Of Radhakrishnan Venkatraman
Sent: Wednesday, February 25, 2009 1:27 PM
To: materials-welding@googlegroups.com
Subject: [MW:1625] Re: 1623] RE: 1622] RE: 1620] PIPE SA106GRB

 

People should think before they are asking such question.This forum is seen by so many experts,by the way they are asking such question shall definitely irritate the experts.
R.Venkatarman 
 


Subject: [MW:1624] RE: 1623] RE: 1622] RE: 1620] PIPE SA106GRB
Date: Wed, 25 Feb 2009 14:52:55 +0700
From: faigal.agbanawag@czfp.com
To: materials-welding@googlegroups.com

Dear Ravi,

 

I believe CKP has a point. This forum is not how learned you are but how you can spare learning to those who wanted to learn.

I am new to the forum and I find it so interesting and helpful. Hoping to pitch in some recommendation in the future.

 

Let’s keep an open mind guys.

 

Regards,

 


Faigal Fernando Agbanawag
Sr. Piping Engineer
Clough ZFP

T

+966 3 8828818 Ext: 241

F

+966 3 8828622

M

+966 (0) 507780576



 

From: materials-welding@googlegroups.com [mailto:materials-welding@googlegroups.com] On Behalf Of Chaitanya Purohit
Sent: Wednesday, February 25, 2009 10:25 AM
To: materials-welding@googlegroups.com
Subject: [MW:1623] RE: 1622] RE: 1620] PIPE SA106GRB

 

Dear Ravi,

 

The intension of joining such forum is to learn more and upgrade yourself. We definitely will have such person who may ask some question like this but as a knowledgeable, mature and senior person we shall not get annoyed for such questions. Instead we shall train them to find the answers for themselves.  

 

Or else if we do not want to see such basic (may be baseless) question better define that this forum is for experts only and no junior person shall raise any question…isn’t it…

 

Don’t feel hurt about my mail but we have to put ourselves in their shoe and think like them.

 

Regards.

 

C. K. Purohit

General Manager - QC

KNM Process Systems Sdn Bhd - Malaysia

 

HP No. : 6016-3376448


From: materials-welding@googlegroups.com [mailto:materials-welding@googlegroups.com] On Behalf Of Yeleswarapu, Ravi
Sent: Wednesday, February 25, 2009 2:41 PM
To: materials-welding@googlegroups.com
Subject: [MW:1622] RE: 1620] PIPE SA106GRB

 

Suggestion,

It is a request to all members to make better use of this forum and refrain from misusing and posting such queries and wasting the valuable forum time/space without doing proper preparatory work. In my opinion cannot be answer for every ‘why’ and need not be discussed.

For following the answer is b’cos the standard states so.

 

From: materials-welding@googlegroups.com [mailto:materials-welding@googlegroups.com] On Behalf Of Srinivasan R.
Sent: Wednesday, February 25, 2009 10:16 AM
To: materials-welding@googlegroups.com
Subject: [MW:1620] PIPE SA106GRB

 

Why SA106GRB  pipe is available only as  seamless pipe and not welded.

 

Regards ,

 

Srinivasan.R

Piping Dept.

 

 


--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to materials-welding@googlegroups.com
To unsubscribe from this group, send email to materials-welding-unsubscribe@googlegroups.com
For more options, visit this group's bolg at http://materials-welding.blogspot.com/
The views expressed/exchnaged in this group are members personel views and meant for educational purposes only, Users must take their own decisions w.r.t. applicable code/standard/contract documents.
-~----------~----~----~----~------~----~------~--~---

No comments:

Re: [MW:34874] ASME IX, groove weld during WQT limits for Fillet Weld production

Hi David,  There are two points in WQT. 1. Thickness of Base Metal -T 2. Thickness of Weld Metal -t When you use a combination of two proces...