Skip to main content

What does a good game consist of? (part 21)

Programmer's Role in Game Development
-part 3:

Why is Coding Hard?

This is the last of the three part miniseries which describes the programmer's role in the game development process.

So how come it's so hard to code something?

 One of the main reasons is the need to be well-prepared for it which most programmers are not. In other words preparation-one or more of the following reasons include lack of being prepared for the task:
  • the programmer is coding by the most difficult thing they learnt, which means they don't do what is in their capability but overstretching
  • lack of test-driven development
  • "determination" to make an average game, which can be boring in both terms of development and playing
  • incomplete GDD
  • lack of problem-solving attitude
  • lack of a productivity plan
So mental preparation is the main problem here: prepare yourself to code better and faster!
  • go step by step, and work with what you have learnt so far, not of what you are currently learning
  • build on small and core chunks of the game
  • be determined to make an above-average game, even if you see no way to do it-the game will be above average, even if for the tiniest notch!
  • make the GDD complete, but not complete as everything being written, but as having everything which a programmer needs to be there
  • have the attitude of "every problem has a solution"
  • decide which techniques or tools you will use for enchanced productivity
Labels:

Comments

Post a Comment

Popular posts from this blog

object oriented programming

Object oriented programming is a sound and bold approach to c++ and internet wiring application and video games. It reduces a lot of code messes, made by global and half global functions. One of the more advanced object programming techniques are private access, poly morph and object message inheritance. It is set by c++ bjarne stroustrup and iso isometric standard convention comitee to use classes instead of structs and structures for making objects. Which means you most definitely should , but not must or have to. class Monster {     std::string memory_attributes{}; public:     void treck();     void track();     void trace(); }; The treck() function makes the monster roam and do human like jogging and trimming. track() means the monster goes ai path tracking and trace() means it tries to find other monsters in the area. class Weapon {     std::string memory_attributes{}; public:    void use(); }; void Weapon::use() {   ...
Post a Comment
Read more

C++ and OOP in a different manner

Keep in mind this article is meant strictly for C++ game devs and not for application programmers or game devs of scripting/other languages. I have my own technique when it comes to OOP in C++. The game I'm deving right now(or we are making) is a simple windows console project. It's up to you to decide whether you'll use this technique. First let me tell you in which cases you might need this technique: if you're ready for a new look on OOP if you need a new toolset for your coding practice if you like to learn(which I clearly hope for) So, the technique then. Decide which you prefer more: classes or structures. This helps you understand what kind of objects you want in a game.
Post a Comment
Read more