How to become a C++ Programmer

1. go to www.google.com and search for any C++ book (but end up with wikibooks.org)
2. read the first and the second chapter.
3. understand nothing, but notice that some parts of C++ look alot like C to you.
4. decide to learn C instead, because you think it would help learning C++.
5. spend 4 months on learning C and catching bugs in your first applications.
6. go back to wikibooks, because you think you are ready to learn C++ now.
7. read the third chapter (which is about OOP).
8. understand nothing. complain. connect to irc.freenode.net and join ##c++ and complain more.
9. someone tells you to try haskell instead.
10. go to www.google.com and search for a haskell book (but end up with wikibooks.org).
11. understand nothing.
12. complain.
15. go back to C++.
16. try to read and understand chapter three again. this time, you manage to grasp the very idea of OOP, and you happily start to mash your head agains the keyboard to write your own Enterprise Helloworld Application (which can be bought for only $299).
17. notice templates.
18. try to learn templates.
19. unable to learn templates.
20. complain about templates.
21. complain more about templates.
22. tell everyone C++ is bloated and shit because you still don't understand templates.
23. try to read the fourth chapter.
24. you still don't quite understand what they could be good for, but at least you know now how they work.
25. you start to write a shitload of classes with templates in it, knowing that nobody will ever use them.
26. start calling yourself an experienced programmer.
27. congratulations, you are now a C++ Programmer!

1. go to www.google.com and search for any Haskell book (but end up with wikibooks.org)
2. read the first and the second chapter.
3. understand nothing, but notice that some parts of Haskell look alot like Scheme to you.
4. decide to learn C instead, because you think it would help learning Haskell.
5. spend 4 months on learning Scheme and catching bugs in your first applications.
6. go back to wikibooks, because you think you are ready to learn Haskell now.
7. read the third chapter (which is about types).
8. understand nothing. complain. connect to irc.freenode.net and join ##haskell and complain more.
9. someone tells you to try C++ instead.
10. go to www.google.com and search for a C++ book (but end up with wikibooks.org).
11. understand nothing.
12. complain.
15. go back to Haskell.
16. try to read and understand chapter three again. this time, you manage to grasp the very idea of types, and you happily start to mash your head agains the keyboard to write your own Catamorphic Curried Functior Helloworld Type (which can be bought for only $299).
17. notice monads.
18. try to learn monads.
19. unable to learn monads.
20. complain about monads.
21. complain more about monads.
22. tell everyone Haskell is bloated and shit because you still don't understand monads.
23. try to read the fourth chapter.
24. you still don't quite understand what they could be good for, but at least you know now how they work.
25. you start to write a shitload of functions with monads in it, knowing that nobody will ever use them.
26. start calling yourself an experienced programmer.
27. congratulations, you are now a Haskell Programmer!

1. Take a few courses in college that make you use C++
2. Graduate
3. Never use C++ ever again

hello?pythonpolice?OPislooseagain.jpg

>>4
We'll need a description of the person or persons causing the problem and a location where the problem is occurring.  Please wait for the next available operator.

>>4
jpg on a text board

Can you base64 encode it for us?

sepples

Don't change these.

Name:		Email:
Entire Thread Thread List