Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQLServerCentral.com
»
Editorials
»
Dude, Your Fly is Open
40 posts, Page 2 of 4
««
1
2
3
4
»
»»
Dude, Your Fly is Open
Rate Topic
Display Mode
Topic Options
Author
Message
Tim Mitchell
Tim Mitchell
Posted Thursday, February 25, 2010 6:43 AM
Ten Centuries
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 4:11 PM
Points: 1,033,
Visits: 2,593
Scott Smith health care consultant (2/25/2010)
... You should work in HR.
In that case, I retract the entire article
Tim Mitchell
SQL Server MVP
www.TimMitchell.net
twitter.com/Tim_Mitchell
Post #872674
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Thursday, February 25, 2010 6:45 AM
SSC-Dedicated
Group: Administrators
Last Login: Today @ 3:26 PM
Points: 31,425,
Visits: 13,738
majorbloodnock (2/25/2010)
Agree totally with the editorial. Constructive criticism is almost always the right thing to do, and if it's not appreciated then at least you know you did the right thing.
I'll also suggest a good rule of thumb (closely linked with Tim's point) is to criticise privately
and congratulate publicly
.
IMHO, of course....
I completely agree here, especially for managers.
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #872676
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Thursday, February 25, 2010 6:49 AM
SSC-Dedicated
Group: Administrators
Last Login: Today @ 3:26 PM
Points: 31,425,
Visits: 13,738
Very nice editorial, Tim, and I'll respond before I head out for a much needed break today.
Whether it's business communication, or posting here on the forum, I think small errors can be brought to someone's attention when you notice them. Not to embarass, but to clarify or help them. If it's more embarassing, or the person might take offense, I think a private attempt to discuss it with them ought to be made. If that doesn't work, then like with security vulnerabilities, I think they might need a (more) public discussion.
The other important thing is to recognize that you might not be right. Go into the constructive criticism with the knowledge that you are expressing how you feel, and could possibly be wrong yourself. Give the other person the chance to defend themselves and be as willing to listen to them as you would like them to be for you.
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #872682
OCTom
OCTom
Posted Thursday, February 25, 2010 6:53 AM
SSCrazy
Group: General Forum Members
Last Login: Today @ 12:55 PM
Points: 2,015,
Visits: 2,847
Sometimes a public unveiling of a mistake is appropriate. For instance, when a team is meeting on a design and someone suggests something that is entirely inappropriate for the application. That is the time to nip the error in the bud. However, one can still be nice about it. That's where diplomacy comes in. And, it's also a great time to educate why the idea is bad to begin with.
I once knew a fellow who would laugh hysterically when someone made a comment or asked a question he thought was stupid. He didn't last long in a team environment.
Most of the folks answering questions on SSC are polite and nice but there are some that could use some humility and patience. The same goes for those asking the questions.
I have been retitcent to post questions and answers here mainly because I risk being taken to the woodshed publicly.
I really appreciate everyone who does volunteer their time here answering questions and creating QOtD's. It's helped me over the last couple of years learning SQL Server on the job.
Post #872687
WayneS
WayneS
Posted Thursday, February 25, 2010 7:02 AM
SSCertifiable
Group: General Forum Members
Last Login: Today @ 4:35 PM
Points: 6,368,
Visits: 8,232
Very good article Tim.
majorbloodnock (2/25/2010)
I'll also suggest a good rule of thumb (closely linked with Tim's point) is to criticise privately
and congratulate publicly
.
and might I add to the congratulate publicly... and often.
The other important thing is to recognize that you might not be right.
How does that concept work?
Seriously, that does bring up that you need to pause to ensure that you are right before telling someone else that they are wrong.
Wayne
Microsoft Certified Master: SQL Server 2008
If you can't explain to another person how the code that you're copying from the internet works, then
DON'T USE IT
on a production system! After all,
you
will be the one supporting it!
Links:
For better assistance in answering your questions
,
How to ask a question
,
Performance Problems
,
Common date/time routines
,
CROSS-TABS and PIVOT tables Part 1
&
Part 2
,
Using APPLY Part 1
&
Part 2
,
Splitting Delimited Strings
Post #872695
jcrawf02
jcrawf02
Posted Thursday, February 25, 2010 7:11 AM
SSCrazy
Group: General Forum Members
Last Login: 2 days ago @ 12:09 PM
Points: 2,550,
Visits: 18,882
I think I will have to disagree with you, for purely selfish reasons, if the setting is a forum such as SSC. With the intarwebz so open to search, if the 'mistake' (small or great) is not pointed out within the same document that it originates from, others (read: I) will stumble upon it when looking for answers and be misled. This is why I come to SSC, because the discussions often lead to a much more profound understanding of what is going on.
That said, the correction should have a modicum of restraint, not "Hey, you idiot, why can't you do anything right?...", but rather "I would disagree, because of X and Y, the correct answer should be Z".
If the setting is in the office, then I would agree that the mistake should be corrected privately, unless it causes critical errors that need fixed immediately, and training needs noted for the group.
---------------------------------------------------------
How best to post your question
How to post performance problems
Tally Table:What it is and how it replaces a loop
"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
Post #872707
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Thursday, February 25, 2010 7:14 AM
SSC-Dedicated
Group: Administrators
Last Login: Today @ 3:26 PM
Points: 31,425,
Visits: 13,738
These forums, I think, do require pointing out of mistakes for the reasons Jay mentioned. However if it's something like a typo, I have pinged people to privately edit their post.
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #872710
Gary Varga
Gary Varga
Posted Thursday, February 25, 2010 7:22 AM
Hall of Fame
Group: General Forum Members
Last Login: Today @ 6:44 AM
Points: 3,536,
Visits: 1,124
Hey, we are all agreeing!!!
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #872721
majorbloodnock
majorbloodnock
Posted Thursday, February 25, 2010 7:34 AM
Ten Centuries
Group: General Forum Members
Last Login: Wednesday, May 01, 2013 9:44 AM
Points: 1,043,
Visits: 2,943
jcrawf02 (2/25/2010)
I think I will have to disagree with you, for purely selfish reasons, if the setting is a forum such as SSC. With the intarwebz so open to search, if the 'mistake' (small or great) is not pointed out within the same document that it originates from, others (read: I) will stumble upon it when looking for answers and be misled. This is why I come to SSC, because the discussions often lead to a much more profound understanding of what is going on.
That said, the correction should have a modicum of restraint, not "Hey, you idiot, why can't you do anything right?...", but rather "I would disagree, because of X and Y, the correct answer should be Z".
If the setting is in the office, then I would agree that the mistake should be corrected privately, unless it causes critical errors that need fixed immediately, and training needs noted for the group.
Let's not forget, though, that threads are inherently designed around discussion, frequently with differing opinions contributing. Even if someone's posted something that turns out to be wrong, they needn't necessarily have to feel embarrassed about making the mistake - especially if it was an easy mistake to make. Moreover, the discussion you're talking about that gives a more profound insight needn't ever become criticism, constructive or otherwise (although I agree it does sometimes descend to that level in practice).
Where someone's committed a real howler that they probably will or ought to be embarrassed about, you've always got PM to have a "quiet" word first, so even though this is a very public medium I believe the basic rules of considerate communication can still be maintained.
Semper in excretia, sumus solum profundum variat
Post #872737
Frank W Fulton Jr
Frank W Fulton Jr
Posted Thursday, February 25, 2010 7:51 AM
SSC Rookie
Group: General Forum Members
Last Login: Monday, April 29, 2013 3:37 PM
Points: 26,
Visits: 112
Not only would I like to be informed, but I would like to be informed sooner rather than later
Post #872751
« Prev Topic
|
Next Topic »
40 posts, Page 2 of 4
««
1
2
3
4
»
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.