• Advertisement
Sign in to follow this  
  • entries
    3
  • comments
    11
  • views
    562

Entries in this blog

 

Expectations for all your code, always

Part 1 It needs to work. And by work I mean execute without crashing. It needs to do what you expect it to do. It needs to have code you can actually read and debug. Part 2 No Syntax Errors No Warnings (from the compiler) It has tests (yes, even asserts) It passes test. It logs errors. It does not crash. Someone who doesn't know you won't kill you for writing completely illegible code. It has instructions. For the user.  

Alpha_ProgDes

 

The 10 Suggestions.

I think for anyone beginning to learn to game dev, you should heed the following Suggestions. I don't care how you do it; just do it. Your language doesn't matter. Your platform doesn't matter. Nothing. Truly NOTHING. Is better or best for game dev. You will struggle. You will get everything wrong. You will write terrible code. You are expected to fail in the most successful way. So just make a game. Are you worried about performance, cross-platform, code smell, or architecture, then GOTO 8. Finish making that game, worry about nothing else. If you want to learn how to make your game better, then show your code and ask questions. If you want to make another game, then GOTO: Step 6.  

Alpha_ProgDes

Sign in to follow this  
  • Advertisement