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

Comments

Popular posts from this blog

Level design basics, part 2

An arch level design is hard, as it doesn't involve only polygon boxes, but also also three dimensional curve lines. If you ever played. Americas army 1, you'll know how hard it is to make a curve building, like the famous over played bridge crossing map. The point is to start. With one curve. Curve is not a straight line, but it's still a line. Means it is possible to apply lines into a three dimensional level. arch 0 0 1 0

Level design basics, part 7

Meta files Meta means in between. Wild hard ware and soft ware connection. A game design level document is just documentation; it is normal text. Actual level files however are en coded. Not normal text, in other words; which is why they are a lot harder to make. Forests for example are hard to put into a text file. Trees are real world eco systems that are the source of nature and life. It is one thing to put a real world object into a game, what is even a LOT harder is putting one, for example a tree into a text file. Source code is just sofware, it is nothing but encoded writing, which is why to put it into soft ware is not exactly easy, but has been done many times before. However, putting source code directly into hard ware is a completely different thing. That's where meta files come in handy. Meta files are clay ware. They work very similiar to a human brain. Like a connection between software and hardware. A meta file contains level game design documentation and level code....

Coding

I find it extremely hard to code a game. It gets worse than that. I also have to do the game design, UI design, level design and the story. Basically lots of bugs, lots to learn, lots to design. The good news is I have a teammate and she works on level design and story. Helps a lot regardless there is tons of work to be done before even first of the three Trix games gets published. I sometimes work even 12 hours a day. Yikes!