# Allmänna råd till (spel-) programmering.
Det här kan hittas i original på www.gamasutra.com . Denna lista är en samling av 30 tips för nybörjare inom spelutveckling. Vissa råd är endast för de som tänker sig bli proffessionella utvecklare och vissa är kanske lite obegipliga för de som har kontakt med programmering för första gången inom kursen Programmering 1. De är uttagen annars var det viss risk för förvvirring eller frustration. Här de för oss relevanta 14. Vi antar att era kunskaper i engelska är tillräckliga:
-
Start with a small game.
-
Finish your first game.
-
If you're developing your first game and you've no idea about game development. Start with tetris / a basic platform game or an arcanoid game. Always get feedback about your game. Start this process immediately after the first prototype is finished. Test your game with a brutally honest group of people who never played your game before.
-
Don't get the critics personal. Getting a feedback like "your game is perfect. I loved it !" does't help you at all. "The control isn't comfortable, levels are getting too hard in a short time" helps you much more. Beware that users aren't criticizing you, they're criticizing your game. If you're developing your own game -please I beg you- don't make a clone game. Nobody needs a another bubble game. Clone game development causes you to not to learn the game design iteration process.
-
Avoid using game engines before having the knowledge of "what is a game engine?", "what is the benefit of using game engine?". Don't start with programs like unity, corona, game maker before knowing what happens in a game loop.
-
Find team mates. They'll motivate you and most importantly being responsable to a teammate is much more motivating then being responsable on yourself.
-
Find a mentor but don't ask questions to your mentor as a reflex. First research the problem, if you're stuck then ask for a keyword. Don't underestimate the power of google. If you think you got a good idea, go for it. Nearly all of the successful indie game's have core mechanics which can be developed in 1-2 weeks. If they weren't continue development they wouldn't be successful.
-
I love the quote of Martin Golding: "Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live." If you think something wrong with your code. Delete it and write it again.
-
Learn how to search on google. Seriously, I mean it. Internet is a big junk if you don't know the right keywords.
-
Before starting developing a game have conversation with your developer friends. Tell them the algorithm that you're about to write or the alternatives in your mind and have a brain storm. This may gain you so much time and it may prevent you taking the wrong rode.
-
If you find your self in a dead end have a break. If it is possible, sleep. Your brain keeps trying to solve the problem. When you wake it's highly possible to shout "eureka". When starting to a new language my learning way is: Find a nice book about -> Read most of it ( you'll forget everything but you'll have the keywords) -> Read some example code and analyze them -> Pick a goal and start writing-> If you get stuck look at the example codes -> If you cant find google the problem -> If you can't find related web sites you don't have the right keywords, ask a friend of yours who knows the language -> Search for the new keyword -> Write until next problem :)
-
Don't make random search. There are lots of things to learn so learn step by step.
-
Learn according to your projects' needs. You'll forget all of the things that you didn't practice. As conficius says “I hear, and I forget. I see, and I remember. I do, and I understand”.
-
Don't afraid of saying "I don't know this, can you tell me". Don't be slave of your ego.