Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 1234»»»

Calling Out Bad Advice Expand / Collapse
Author
Message
Posted Tuesday, December 21, 2010 9:23 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, December 11, 2014 9:19 AM
Points: 1,046, Visits: 2,739
Comments posted to this topic are about the item Calling Out Bad Advice



Tim Mitchell, SQL Server MVP
Independent Business Intelligence Consultant
www.TimMitchell.net
@Tim_Mitchell

Post #1038054
Posted Tuesday, December 21, 2010 9:52 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, October 9, 2014 1:02 PM
Points: 6,032, Visits: 5,284
I tend to like to use the "I believe you are mistaken" route, and here is a URL clearing it up?

I also have to agree that every post and every article and every blog post puts your skills on display. I know that for me there was a certain level of angst when I first submitted my articles for publication here.

I've been doing this for a long time and many things are not right vs. wrong but style. But I too have seen outright wrong advice and it needs to be combatted.

CEWI
Post #1038063
Posted Tuesday, December 21, 2010 11:41 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 2:03 PM
Points: 1,334, Visits: 3,069
No one ever gets it 100% right every single time they post on on a forum to my knowledage anyway. That is why we call them FORUMS. They are a meeting place for debate and discussion. They don't claim to be factual sources like encyclopedias, MSDN, or BOL (and even those have known to be wrong in the past as well). Most people here can put up with the occasional error you might see on a forum post (or even an article or BLOG) versus the overwhelming accurate and very helpful information these forums and this site do provide. It's not that big of deal in the big picture IMHO.

"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ..."
Post #1038081
Posted Wednesday, December 22, 2010 2:32 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, March 17, 2014 5:28 AM
Points: 10, Visits: 60
Most true professionals due a good job of self-screening,


Not here, it seems

A correction is due, if you do not mind...
Post #1038124
Posted Wednesday, December 22, 2010 5:21 AM


UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: Friday, December 12, 2014 5:05 AM
Points: 1,453, Visits: 1,856
I would say giving feedback on an write-up is more like doing a peer-review. When we review code, we try to not use words like "you" or "me" or even the name of the developer. We always say and write "the code...". This is a conscious effort on the part of the reviewer and does help a lot in keeping personal/emotional effects at bay.

Here's what can be done:
There can be a feedback center (or a small checkbox at the bottom of the editor, near the "save/post" buttons) where users can directly reference the particular article or piece of information that one finds to be incorrect and add their comments. A discreet Email can be sent out to the originator of the article, who can then take the corrective action while a visual indicator set on the piece indicates pending changes to all new visitors.

No names disclosed, no emotional angle attached and hence, no harm done.

At all costs, everyone who reads a write-up should keep in mind that the poster has spent some time and energy to research and share something with the world. That is worth appreciating, and some minor errors (unless technically incorrect) should be ignored.


Thanks & Regards,
Nakul Vachhrajani.
http://nakulvachhrajani.com
Be courteous. Drive responsibly.

Follow me on
Twitter: @sqltwins
Google Plus: +Nakul
Post #1038198
Posted Wednesday, December 22, 2010 6:14 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, October 27, 2014 11:15 AM
Points: 2,041, Visits: 1,671
The vast majority of the time I try to be very supportive when giving constructive criticism, but sometimes if the person *repeatedly* posts incorrect things, a harsh wake-up call is warranted IMHO. I did just that a week or so ago on Twitter (maybe the incident to which you're referring Tim?) because the advice was so blatantly misleading from such a widely read blog - it would have had many DBAs struggling to figure out why their system wasn't exhibiting the behavior specified. That's incredibly unhelpful and damaging and needed to be put right immediately, especially as the blog post in question had just been widely RT'd around the community.

I've seen the same thing happen on the MSDN forums with people that constantly reply with dubious or downright misleading information, and I've seen SQL Server Magazine publish un-reviewed articles that speak of regularly shrinking databases - which provoked a wide backlash and a retraction.

Sometimes it can be difficult to figure out what method to take when correcting bad advice, as you especially have to be 100% certain that what you're correcting is, in fact, bad advice.

But good editorial!


Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Post #1038214
Posted Wednesday, December 22, 2010 6:34 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, May 19, 2014 9:26 AM
Points: 312, Visits: 1,028
In many cases I have seen misleading blog posts or replies have their origins in some paper or information published by MS itself and not cleared up later. I have myself had two issues with MS on widely accepted problem issues - the problem with GUIDs and fragmentation, and the problem with # of tempdb files being equal to the # of cores. Granted i didnt speak to someone at the top at MS, mostly the CSS engineers and our TAM, but they were not able to give me a MS link that agreed to these two issues as often explained by well known authorities such as Kim and Paul. (Perhaps there is one now, this was a year or so ago).Where i work for example the management is not very well educated on who is an authority on SQL and who is not outside of MS, they go largely by the book. MS needs to update and correct documentation on a much more frequent basis, and perhaps remove what has been proven outdated.

On how the correction should be made, yes I think Paul is right, people can and should be called out when they have a wide audience and post misleading info. But perhaps writing to them personally would be better than doing so in public. Just my 2 cents.
Post #1038224
Posted Wednesday, December 22, 2010 6:39 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, November 3, 2014 2:42 PM
Points: 1,683, Visits: 1,798
One of my favorite topics, and a very difficult one at that. I personally handle things differently depending on the who/what/where of the content. Inaccuracies on the forums is one thing, and people are a bit more likely to read through the majority of comments on a forums post before deciding to follow advice. An article or newsletter from a major publishing site like SQL Server Central, or the competetors that is blatently wrong; Game On, because the editors should have done a better job before publishing incorrect content.

Experience shows that fewer people read the comments on Articles than forums, especially when they have to click a Join the Discussion button to find the comments. Some really bad articles have pages of comments correcting wrong information, and the authors never fixed the article, which is possible to do, I've made changes to my own Articles on here when information changed with Service Packs, or through further understanding. Expecting that the Discussion forums for an Article will police your bad content is wrong thinking, and that's not targeted at SSC, but the community at large because it happens all over.


Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs
Post #1038231
Posted Wednesday, December 22, 2010 6:44 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 2:44 PM
Points: 2,666, Visits: 4,089
My 2 cents worth:

When correcting/criticising someone:

1. Don't make it personal.
2. Make it about the code and/or advice.
3. Use positive instead of negative terms.
4. Give an alternative and explain why it's better.

When being corrected/criticised:

1. Don't take it personally.
2. Remember it's about the code and/or advice.
3. If you are wrong, accept the criticism/correction gracefully.
4. If you are not wrong, use the first four steps above to correct the corrector.

And, for both, remember there are many ways to accomplish a task or solve a problem. Your way may be just one of many and it may not work in all installations.
Post #1038237
Posted Wednesday, December 22, 2010 7:11 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, December 11, 2014 9:19 AM
Points: 1,046, Visits: 2,739
lenne_dk (12/22/2010)
Most true professionals due a good job of self-screening,


Not here, it seems

A correction is due, if you do not mind...


Indeed, sir! Thanks for pointing this out, I missed it during the edit.




Tim Mitchell, SQL Server MVP
Independent Business Intelligence Consultant
www.TimMitchell.net
@Tim_Mitchell

Post #1038254
« Prev Topic | Next Topic »

Add to briefcase 1234»»»

Permissions Expand / Collapse