Re: [Dev-C++] (no subject)

[jose i. c. <ji...@gm...>]

Jay,

wrong!  I do my own research, read my books and do my homework.=20
Though, I am been known to ask a question here and there.=20
Nonetheless, there is a difference between saying,

"The good way to start programming is by doing research on the
internet, books, newsgroup, etc.  What you are trying to do, many
other folks have already done.  So, i would suggest for you, "such and
such" book, by "such and such" author.  I also suggest www.cpp.org and
www.someothercpp.org and www.anotherwebsite.com has been extremely
helpful to me.  You may want to give those a try and when you get
stuck, come back and ask us.  We'll be here waiting.  By the way,
happy programming!"

and let the guy go with a bunch of knowledge and thinking that we are
nice people.  But putting the guy down like that it makes no sense.=20
You know, many people hate us c/c++ programmers because we are nasty.=20
Not because we are smart, which we are, but because we are nasty to
people and other programmers.  We love to show our wisdom and how
smart we are and how great and short our code is and how...  I guess
that comes with the geeky side of us, but friends, it's a bad
reputation we geeky people have, which we should change: we are
socially challenged.

Just a thought...

Back to programming...

On 4/13/05, Jay Blanchard <jay...@ni...> wrote:
> [snip]
> Was that really needed?
>=20
> Don't help, if you don't want to help.
> [/snip]
>=20
> You'r eprobably one of those guys who got his feelings hurt when someone
> told them to RTFM or STFW, aren't you? Honestly, I'd rather teach a man
> to fish any day. He will learn more. There are thousands of tutorials on
> C++ programming on the web and any new programmer would gain value from
> them and the ability to find them. You didn't help out either, did you?
> Don't throw rocks unless you want them thrown back.
>=20
> Here is some sage advice from another list...
>=20
> 1. Try http://www.google.com  Searching for "C++ YOUR QUERY" may fetch
> your relevant information within the first 10 results.
>=20
> 2. There is a searchable archive of the mailing list discussion online.
> Many of the common topics are discussed
> repeatedly, and you may get answer to your query from the earlier
> discussions.
>=20
> For example: One of the repeatedly discussed question in the list is
> "Best C++ compiler". Everyone has his/her favourite editor. You can get
> all the opinions by going through the list archives.
>=20
> 3. If you are stuck with code and do not understand what is wrong,
> instead of posting the whole shebang, post the relevant portion of the
> code
>=20
> 4. Provide a clear descriptive subject line. Avoid general subjects like
> "Help!!", "A Question" etc. Especially avoid blank subjects.
>=20
> 5. When you want to start a new topic, open a new mail composer and
> enter the mailing list address instead of replying to an existing thread
> and replacing the subject and body with your message.
>=20
> 6. It's always a good idea to post back to the list once you've solved
> your problem. People usually add [SOLVED] to the subject line of their
> email when posting solutions. By posting your solution you're helping
> the next person with the same question.
>=20
> 7. Ask smart questions http://catb.org/~esr/faqs/smart-questions.html
>=20
> 8. Do not send your email to the list with attachments. If you don't
> have a place to upload your code, try the many pastebin websites (such
> as www.pastebin.com).
>=20
> 9. "Because it is hard to read."
>   "Why?"
>   "Top-postng is bad."
>