| re: Advice for reacting to critical posts
Speaking of people only concerned with scoring rhetoric points - please
ignore the troll.
[And ignore the plagiarism which is common around here.]
"Steve Jorgensen" <nospam@nospam.nospam> wrote in message
news:8ckfi01qd11m6h83c778qoa8dngddeb93s@4ax.com...[color=blue]
> I'm posting this message because what's kept me around here all these[/color]
years is[color=blue]
> the love of being helpful on a subject I know a lot about (and sometimes[/color]
of[color=blue]
> looking smart, but hopefully more about being helpful).
>
> Sometimes, there's just no nice and fuzzy way to respond with advice to
> something one thinks is wrong, and in the past, I've often chosen to hedge[/color]
and[color=blue]
> hint rather than confront directly. While that's not very threatening, it
> also doesn't always communicate much information or express the strength[/color]
of my[color=blue]
> opinion or my confidence in my answer.
>
> Anyway, the following are my suggestions to people who are taken aback by[/color]
a[color=blue]
> reply from me or anyone more direct (and possibly more informative) than I[/color]
who[color=blue]
> also posts and replies on this group.
>
> 1. Don't take personal offense when someone questions one of your[/color]
technical[color=blue]
> opinions, practices, or code samples.
>
> 2. If you disagree with the respondent on a technical level, express your
> disagreement, and do so on a technical level. If you're right, perhaps[/color]
he/she[color=blue]
> will be convinced, perhaps not. That's fine.
>
> 3. The respondent is probably not 100% right, and neither are you.
>
> 4. It is helpful to have a dialog, and have each participant and lurker[/color]
arrive[color=blue]
> at their own best opinions and conclusions after a proper and[/color]
dispassionate[color=blue]
> consideration of all available opinions and measurements. It's not[/color]
terribly[color=blue]
> important for some "more correct" person to "win" some argument or score[/color]
some[color=blue]
> rhetoric points.
>
> 5. It's OK to let a thread fizzle after all points have been expressed and[/color]
no[color=blue]
> agreement has been reached.[/color]
| 
