|Anyway what was this about?|
|I have a good advice for you - be humble. If you don't act like you know everything, you can learn a lot and open your mind. If you act like you know best, then you won't make progress.|
|Man, I'm 18, and I don't claim that I know everything about C++/programming/programming languages. You are 12 and talk like you were the guru.|
|You don't know everything about C++|
|Also, just because you're Eighteen doesn't mean anything.|
|In some problems C++ is infact faster than C.|
I can't find the page that had an example, but if I do I will post it here.
But what's the interpreter written in? C. That's why is slower. It's a combo.
However you can't get that into Java fanboy's heads. They have the mindset that Java's faster than C apps when the very interpreter is programmed in C. That's why it's useless talking to them. It's a waste of energy to open your mouth(or type words) to do that. Plain and simple
Man, I'm 18, and I don't claim that I know everything about C++/programming/programming languages. You are 12 and talk like you were the guru.
|You don't know everything about C++. Not even Bjarne does.|
|The creator of the language who made it everything it is doesn't know everything.|
|How did what I type seem like I was a guru or something?|
|Well I don't try to post as one, I guess it just comes out that way.|
I started to "help" the people outside the lounge because you guys said I didn't do anything and I only posted in the lounge.
I guess I can't please anyone?
|I honestly just try to solve other people's problems as fast as possible doing the least amount of work. Bad practices maybe?|
|How To Answer Questions in a Helpful Way|
Be gentle. Problem-related stress can make people seem rude or stupid even when they're not.
Reply to a first offender off-line. There is no need of public humiliation for someone who may have made an honest mistake. A real newbie may not know how to search archives or where the FAQ is stored or posted.
If you don't know for sure, say so! A wrong but authoritative-sounding answer is worse than none at all. Don't point anyone down a wrong path simply because it's fun to sound like an expert. Be humble and honest; set a good example for both the querent and your peers.
If you can't help, don't hinder. Don't make jokes about procedures that could trash the user's setup — the poor sap might interpret these as instructions.
Ask probing questions to elicit more details. If you're good at this, the querent will learn something — and so might you. Try to turn the bad question into a good one; remember we were all newbies once.
While muttering RTFM is sometimes justified when replying to someone who is just a lazy slob, a pointer to documentation (even if it's just a suggestion to google for a key phrase) is better.
If you're going to answer the question at all, give good value. Don't suggest kludgy workarounds when somebody is using the wrong tool or approach. Suggest good tools. Reframe the question.
|freds actually quoting me and i stand by it. lets say i write a dll or a header or something that adds an api to c++ for i dont know, making web-pages. if i didnt publish it, then bajarne would have no knowledge of that. while he probably knows the standard inside and out, what i and i think fredbill mean is that he cant possibly know everything that was produced by c++ and made a part of it|