| Author |
Topic |
|
M.E.
Aged Yak Warrior
539 Posts |
 Posted - 2002-05-16 : 13:53:44
|
| I seem to be good at finding answers that are close to the solution but not exact (or in some cases somewhere off in left field). Now the question... Should you be completely sure your answer is going to be correct? Or is it better to post up an idea that may not be right but has a chance of pointing them in the right direction? |
|
|
graz
Chief SQLTeam Crack Dealer
4149 Posts |
Posted - 2002-05-16 : 14:06:20
|
Which type of answer would you prefer to a question?If you're posting something that is a "look in this direction" kind of answer I'd CLEARLY identify it as such. If you're not sure it will actually work and it's just a guess, I'd also CLEARLY label it as such. Posting something blatantly incorrect seems to draw a fast and harsh response  I'd also pay attention to how much time has elapsed since the question was posted. If someone posted a question two minutes ago and you only have a guess then you should probably consider holding off. If someone posted a question yesterday (weekends don't count) and no one has answered it then maybe your guess is the best they'll get.===============================================Creating tomorrow's legacy systems today.One crisis at a time. |
 |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2002-05-16 : 18:59:40
|
Graz, was that an exact answer, or were you just pointing him in the right direction?  Because you started with a question, I thought maybe you were just pointing him in the right direction, but you didn't label it as such, so maybe it was exact...  |
|
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2002-05-16 : 19:33:34
|
I agree with Graz, but I will add a few things.I tend to give general answers sometimes. Pseudo-code and things like that, or a description of what to do. This is because I want people to have to put a little bit of thought into it. If they provide good DDL or something else that makes it easy for me to post exact code I will. So don't be afraid to only give direction rather than exact code to someone that hasn't done their bit to help you find them a solution.Sometimes people don't accept this and want you to give them all the code from guesswork.  With what Graz said about posting incorrect answers. This will be doubled if someone has posted a correct solution, and you post an incorrect one immediately after. Or add something useless just to get a post in (Unless it is a beer or Yak reference).But I agree that if you start by saying you are not totally sure but here is an idea that might work, you will be fine.And lastly, admit when you are wrong. There have been cases of people arguing for days when they are clearly in the wrong and have been told so by people who know better.Damian |
|
|
|
rrb
SQLTeam Poet Laureate
1479 Posts |
Posted - 2002-05-17 : 04:28:44
|
My approach is to put as much arse (that's ass for the yank-tanks) and as little class as possible.  I reckon it's simple - if you're not sure - let them know... (and if you're DAMN sure, then leave a note asking for byrmol to correct you later....)--I hope that when I die someone will say of me "That guy sure owed me a lot of money" |
|
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2002-05-17 : 08:56:02
|
quote:
then leave a note asking for byrmol to correct you later....)
Or not, because he will anyway...or just come up with a better solution and make you look like an idiot  Damian |
|
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-05-17 : 09:24:28
|
quote:
Or not, because he will anyway...or just come up with a better solution and make you look like an idiot
put diff. The further you stick out your neck, the more likely it is someone will drop the axe on it. I don't know about you, but I hate looking/acting/smelling stooopid . . . especially when someone points it out . . . Part of the addiction to SQLTeam is you learn something by researching someone else's problem. If you just take a guess, you aren't really bettering yourself. That's not to say it's wrong to just take a guess sometimes, but you (and the question-asking-party) will be much better off if you actually figure out the answer. Quite often, I'll work on someone's problem, because it intrests me, but if I don't come up with a good solution, I won't even post.Most importantly, try to remain positive about people. Its kinda easy to get caught up in the moment, and call someone an idiot . . . Don't bother . . .<O> |
|
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2002-05-17 : 09:30:59
|
| Yeah, you don't wanna get caught up and do anything rash do you ? Damian |
|
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-05-17 : 10:06:01
|
I lost a good friend to one of those rashes... <O> |
|
|
|
M.E.
Aged Yak Warrior
539 Posts |
Posted - 2002-05-17 : 11:30:02
|
| I'm beginning to see why its called the 'Dreaded social forum'heh |
|
|
|
Nazim
A custom title
1408 Posts |
Posted - 2002-05-18 : 03:35:45
|
| I Agree with Graz . but on more then one occation i have been guilty of being reckless. i post what i feel is right(lot of times therez noway you can tell what is the correct solution) . At times i post though am not too confident about it , i know if am wrong i will be corrected. its pretty ok with me if someone points out my stupidity that basically makes me doubly careful when i post next time. whenever am not sure about my answer .i usually add a IMHO or AFAIK. so that i can always keep the escape door open -------------------------------------------------------------- |
|
|
|
|
Better to keep mouth shut, or post if ya can?