Forum Moderators: open
That's part of the reason we aren't fond of urls and specific code problems. We'd rather teach people how to find the answers themselves through authoritative sources. It's the old teach a man to fish thing.
We don't want to quote joe's site down the street for an answer to a CSS/HTML problem, we want to show people where the answer is in the appropriate w3c standards recommendations. When we do that, we all learn from it - not just the guy with the problem.
We could set here and answer "do my homework - give me an answer on a silver platter" type posts all day long;, but who learns from that? If we instead talk about where the answer is in the appropriate specification or manual, we all brush up on it. Whether that is the w3c, a browser manual, or an equally authoritative source, we all know where to go next time. Educators and tutors first - code assistants second.
A few weeks ago, I had a friend email me with a specific css problem. He's built hundreds of sites over the last few years and is a huge commercial success at it. Not being the CSSguy, I deferred to the CSS2 manual on the problem. He said he would buy the CSS2 recommendation, but couldn't find it on Amazon ;-) After my intial shock wore off and I started explaining the w3c too him, he was a bit stunned that he didn't know a thing about it.
(edited by: Marcia at 3:32 am (utc) on May 26, 2002)
As in "...teach a man to fish, and he'll be out of your hair all weekend"? :)
and probably without hair by then too... LOL :)
