|
|
Posted by Michael Laplante on 05/03/06 19:30
"kchayka" <usenet@c-net.us> wrote in message
news:4bqp10F12tej2U1@individual.net...
> Michael Laplante wrote:
FWIW:
1. Don't help or even respond to a post if you don't have a genuine intent
to help.
2. Don't patronize and tell someone they don't understand their problem. If
you don't have enough information, ask for details. I'm an engineer
myself -- I don't presume to know anything about the problem until I have
all the information. Sometimes people don't realize they might still have
useful information. I'm the expert not them. I ask questions first, draw the
information out, experiment and play around with that information, draw
conclusions and make recommendations. (Standard engineering / scientific
methodology. . .)
3. If you don't have an answer due to lack of time, whatever, don't fake it
with the first thing that pops out of your head. People can tell when you're
guessing, then your entire professionalism comes into doubt.
4. If you're going to show off your web prowess -- especially after laughing
at sites that appear to be recognized by the industry itself -- it better be
something breathtaking. Not something so mindnumbingly banal in it's concept
and execution that it could have just as easily been done with tables.
(Tables would have been better anyway because your site didn't validate and
breaks in FF.)
I'm sure you've memorized every HTML / CSS tag and attribute there is and
can whip up code faster than an omelet. However, there's a big difference
between a mechanic and an automotive engineer. I'm not either but I know
enough about cars to be able to tell the difference. (Metaphor. . .)
You want to improve yourself as a teacher and guide, review the thread and
take some lessons from others. . .
M
Navigation:
[Reply to this message]
|