Discussion board A$$holes
-
I agree. I learn countless new things trying to figure one thing out. My personnal favorite is to grab someones class and add to it. Forcing me to learn the technique of there personnal style while learing how to add what I want to it. It does not always work out well, sometimes it doesn't work. My point still stands, if you can't be nice answering the question do not respond. If no one tells the guy what data type a
wParamis, then he will eventualy figure it out on his own. It is aUINTby the way. Can't we all just get along? Darroll Not one person lives in the present. Only the past. I can prove it.Darroll wrote: It is a UINT by the way. It's a
WORDactually :-D -- Iron Maiden (Harris/Gers) wrote: The rebel of yesterday, tomorrow's fool Who are you kidding being that cool? -
Darroll wrote: It is a UINT by the way. It's a
WORDactually :-D -- Iron Maiden (Harris/Gers) wrote: The rebel of yesterday, tomorrow's fool Who are you kidding being that cool?Jörgen Sigvardsson wrote: Darroll wrote: It is a UINT by the way. It's a WORD actually Actually, it's a WPARAM .:-D:-D In Win32, a WPARAM is now typedef'ed as a UINT_PTR. A UINT_PTR is typedef'ed as an unsigned __int3264 (it will be 64 bits long in 64-bit windows.)
-
I agree. I learn countless new things trying to figure one thing out. My personnal favorite is to grab someones class and add to it. Forcing me to learn the technique of there personnal style while learing how to add what I want to it. It does not always work out well, sometimes it doesn't work. My point still stands, if you can't be nice answering the question do not respond. If no one tells the guy what data type a
wParamis, then he will eventualy figure it out on his own. It is aUINTby the way. Can't we all just get along? Darroll Not one person lives in the present. Only the past. I can prove it.y point still stands, if you can't be nice answering the question do not respond. If no one tells the guy what data type a wParam is, then he will eventualy figure it out on his own. It is a UINT by the way. Technically, it's a WPARAM... ------- signature starts "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 Please review the Legal Disclaimer in my bio. ------- signature ends
-
Why is it that amongst people who really help out there are a few people that think that there time is too precious to answer a newbie's questions without coming off like an ass, and asking if they spent any time at all looking it up. I have found that MSDN (WEB) is not organized too well. I would hate to browse that to get all my info. It is a lot easier to just ask someone for help. If it is not worth your time to answer cordially then do not respond. I hate it when people come off smug. There are a few things I need to still learn. Maybe they are easy to look up; maybe I couldn't find it due to not having MSDN CD. I do but still, there are those who do not. Also remember some people need to have the info delivered in plain English when they start out. Just please be nice. If you have a good reason to be an ass please share. Help me understand. Darroll Not one person lives in the present. Only the past. I can prove it.
I have given up on answering a lot of stuff online. Reasons. 1. When you suggest to some folk they check an article that explains there question they get upset. 2. People asking the same question repeatedly without bothering to use simple search tools to find there answer. 3. When you help somebody they start pestering you by email for more info. 4. .... { The list continues ) AFAIC: People should at least spend a day or so working on a problem before seeking external help. These days there is an incredible amount of knowledge available online without having to request personal assistance, and learning how to access that knowledge is one of the best skills a developerer can now learn. Regardz Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining. Said by Roger Wright about me.
-
I have given up on answering a lot of stuff online. Reasons. 1. When you suggest to some folk they check an article that explains there question they get upset. 2. People asking the same question repeatedly without bothering to use simple search tools to find there answer. 3. When you help somebody they start pestering you by email for more info. 4. .... { The list continues ) AFAIC: People should at least spend a day or so working on a problem before seeking external help. These days there is an incredible amount of knowledge available online without having to request personal assistance, and learning how to access that knowledge is one of the best skills a developerer can now learn. Regardz Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining. Said by Roger Wright about me.
Besides what seems like the obvious of doing a simple search on Google, msdn.microsoft.com or even the include files, what amazes me is how many times simple experimentation would provide an answer. Any decent engineer will have one or more projects devoted exclusively to testing. I have several, including one instrumented so I can measure performance in CPU cycles. (BTW, what percentage of programming questions are from students doing their homework? I suspect it may be higher than 50%.)
-
Why is it that amongst people who really help out there are a few people that think that there time is too precious to answer a newbie's questions without coming off like an ass, and asking if they spent any time at all looking it up. I have found that MSDN (WEB) is not organized too well. I would hate to browse that to get all my info. It is a lot easier to just ask someone for help. If it is not worth your time to answer cordially then do not respond. I hate it when people come off smug. There are a few things I need to still learn. Maybe they are easy to look up; maybe I couldn't find it due to not having MSDN CD. I do but still, there are those who do not. Also remember some people need to have the info delivered in plain English when they start out. Just please be nice. If you have a good reason to be an ass please share. Help me understand. Darroll Not one person lives in the present. Only the past. I can prove it.
Let me get this straight. Your time is too valuable to do a few simple searches first before asking your question, but knowledgeable peoples time who are probably much busier than you is not? 9 times out of 10, a lot of questions can be answered with a simple search. I can't count the number of times i've entered exactly what the user was asking into Google and have the answer appear as the FIRST hit. If the answer is really difficult, I don't think anyone is going to be an "asshole" about it, but if the solution is ridiculously easy to find, I have a problem. It's a simple lack of courtesy to at least TRY to solve the problem first before asking. I agree with you that the MSDN isn't always the easiest place to find information, but that doesn't excuse you from trying first. -- Where are we going? And why am I in this handbasket?
-
Let me get this straight. Your time is too valuable to do a few simple searches first before asking your question, but knowledgeable peoples time who are probably much busier than you is not? 9 times out of 10, a lot of questions can be answered with a simple search. I can't count the number of times i've entered exactly what the user was asking into Google and have the answer appear as the FIRST hit. If the answer is really difficult, I don't think anyone is going to be an "asshole" about it, but if the solution is ridiculously easy to find, I have a problem. It's a simple lack of courtesy to at least TRY to solve the problem first before asking. I agree with you that the MSDN isn't always the easiest place to find information, but that doesn't excuse you from trying first. -- Where are we going? And why am I in this handbasket?
My only point is why be an ass about it? Just don't waste your time answering. There is simply no excuse to be an ass. Be nice or don't respond. That is my only point. Darroll Not one person lives in the present. Only the past. I can prove it.
-
y point still stands, if you can't be nice answering the question do not respond. If no one tells the guy what data type a wParam is, then he will eventualy figure it out on his own. It is a UINT by the way. Technically, it's a WPARAM... ------- signature starts "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 Please review the Legal Disclaimer in my bio. ------- signature ends
John Simmons / outlaw programmer wrote: Technically, it's a WPARAM... ...and there I was all excited like, ready for a typical John Simmons blast and instead an informative and reasonable reply. What happened? ;P Michael Martin Australia mjm68@tpg.com.au "I personally love it because I can get as down and dirty as I want on the backend, while also being able to dabble with fun scripting and presentation games on the front end." - Chris Maunder 15/07/2002
-
Why is it that amongst people who really help out there are a few people that think that there time is too precious to answer a newbie's questions without coming off like an ass, and asking if they spent any time at all looking it up. I have found that MSDN (WEB) is not organized too well. I would hate to browse that to get all my info. It is a lot easier to just ask someone for help. If it is not worth your time to answer cordially then do not respond. I hate it when people come off smug. There are a few things I need to still learn. Maybe they are easy to look up; maybe I couldn't find it due to not having MSDN CD. I do but still, there are those who do not. Also remember some people need to have the info delivered in plain English when they start out. Just please be nice. If you have a good reason to be an ass please share. Help me understand. Darroll Not one person lives in the present. Only the past. I can prove it.
First, you should remember that those who ANSWER don't get anything for their answers. They just do it to help other people. And even if their help is selective, it is still help. Those who ASK get (or expect to get) something useful out of their question. So it's quite natural to expect some kind of culture from people who want their questions to be addressed. Several things that I dislike: 1. A lot of questions can be resolved in 5 minutes by typing a couple of keywords in Google. 2. Sometimes when people don't get answers they feel offended and blame other newsgroup/forum readers. 3. I've seen many times questions posted in newsgroup that included such comment: "Please email the answer directly, because I don't usually visit this newsgroup". So they want free support, but they don't even bother to check the newsgroup - the answer must be sent directly. And they don't care about answer posted in a newsgroup, so other people can read it. 4. Questions like "Everybody is talking about Web services, what is it?" don't really deserve to be answered. People need to make their own efforts to obtain basic information. But a question "Can you please give me URLs of places explaining Web services?" is quite okay. So if I stick to your harsh terminology, there are more assholes among those who ask than those who answer :) Vagif Abilov MCP (Visual C++) Oslo, Norway Hex is for sissies. Real men use binary. And the most hardcore types use only zeros - uppercase zeros and lowercase zeros. Tomasz Sowinski
-
John Simmons / outlaw programmer wrote: Technically, it's a WPARAM... ...and there I was all excited like, ready for a typical John Simmons blast and instead an informative and reasonable reply. What happened? ;P Michael Martin Australia mjm68@tpg.com.au "I personally love it because I can get as down and dirty as I want on the backend, while also being able to dabble with fun scripting and presentation games on the front end." - Chris Maunder 15/07/2002
If it will help deal with it better, you can rest assured that I was trying to be a smartass... :) ------- signature starts "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 Please review the Legal Disclaimer in my bio. ------- signature ends
