I'll I have to second this notion. Actually, I'm not sure that discussions on Style are even useful on this forum. If someone asked me why I value the UT, I would have to mimic the Real Estate industry and reply: "Information, Information, Information". I come here to either get it or give it (if I'm able). There may be some other reasons, such as get a good laugh, or a sense of community, but those are incidental - not the real reason. I was trying to follow this thread on the discussion based on the question posed, but I gave up because I had to flip through page after page of editorials on manners, experience, personality, and such.
This is first and foremost a technical forum. Lets keep it that way. I don't come here for comfort or even respect. I come here for knowledge and ideas. If I posted a question and the only response I got was: "You moron, everyone knows the answer is bla bla bla...", I would go away thinking: "Wow, I got an answer to my problem". Sure, my ego might take a hit, but I got a solution, and that's what I really wanted in the first place. If I want to feel good about myself, I'll go spend time with family and friends.
Ok, some people may have a style that's hard to tolerate. But if you learn something, even just a little something, you're the better for it.
Another argument that is somewhat out of place here is what is fact and what is conjecture. Not every solution works for everyone. Everyone agrees to that. I consider nothing I read here as fact until it works for me. Why would I argue that it has to work for someone else? If you feel a solution is not appropriate, suggest another one. What's wrong with that? Developers are free to try what they want, and decide for themselves what works.
Suppose I posted a question here, and got two responses:
1) The first response was a technically precise solution, which I find produces exact results. However, it requires many undesirable changes to my project.
2) The second response was technically inaccurate, using the wrong API call, or had a syntax error. However, I was able to understand the technique used, and the modified solution produced the results I wanted.
Which solution was correct?
To me, the second one. To someone else, maybe the first.

Let's solve the problems, people!

Mark

>If anyone has a problem with the approach someone takes, that is a style [or personality] issue between the approacher and approachee[s], and I have no problem with anyone debating someone's style or approach. If your problem is with the technical merit [substance] of whatever is being discussed, argue those points. However, I do have a problem using style as an arguement against the substance. My primary point of this entire response is to remind everyone to base your arguements appropriately, regardless of whether you are debating substance, style or both
>
>Now to the pertinent comments I have regarding listening to presentations. When I am going to invest my time [and sometimes $$$], I want to be able to take the information provided, apply it and have it work. Theory and canned demos that always work only get you so far. When it comes down to showtime, too often there are missing details critical to what you are trying to accomplish.
>
>I have already paid my substantial registration fee for DevCon as I am sure many of you have. What do you expect to get out of DevCon? A bunch of theory that may or may not work when you get back home and try it for yourself? Not me. As the saying goes, The Devil is in the details.