October 11th, 2007, 02:20 PM
Here's the standard advice:
Learn a language so well that you don't have to ask for broad advice. Only then can you even possibly be ready.
In other words, if you like C++, learn C++ so well that if you want to make a game and you know approximately what it's going to be like your posts will be asking "Hey, here's some code and for some reason it's giving me a wrong value, what's up?" instead of "Hey, want to tell me how I can go about making a game?"
Chat Server Project & Tutorial | WiFi-remote-control sailboat (building) | Joke Thread
“Rational thinkers deplore the excesses of democracy; it abuses the individual and elevates the mob. The death of Socrates was its finest fruit.”
Use XXX in a comment to flag something that is bogus but works. Use FIXME to flag something that is bogus and broken. Use TODO to leave yourself reminders. Calling a program finished before all these points are checked off is lazy.
-Partial Credit: Sun
If I ask you to redescribe your problem, it's because when you describe issues in detail, you often get a *click* and you suddenly know the solutions.