Skip to main content

Game development is hard (part 2)

People understand the game development as something very exciting,
and it is, but that doesn't make it an easy task, in fact far from it.
All game development, especially coding is hard. And all good games

that were ever made, were or are big projects. It takes money and
effort to make an out-standing game, that will people will play for
decades.  Personally, I find coding the hardest part of all game

development. Most people think that becoming and being a coder only
requires schooling, learning coding every day and coding. But the
truth is that coding is hard. It takes a lot of studying and coding.

Having a MIT degree won't hurt anyone, either. Game coder is a vital
and crucial position in a game development team of a business or a
corporate company. The most important part of the development team, in

other words. I am not saying that game art and level design and game
design are not hard either, but coding is a notable exception. My
main advice when it comes to coding, is:

1.write a line of code
2.repeat

In other words, practice coding. Here is a good c++ learn link:

www.learncpp.com

But real learning of c++ comes from having a lot of personal
experience, not from reading tutorials. And here I am not referring to
practice versus theory. Theory is just as important as practice(in

spite of lower priority). What I mean by personal experience is to
just write a lot of lines of code every day. What regards game design
and level design, I could suggest making design images instead by

painting(=microsoft paint).

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

Coding and game development, part 2

 Consider the following C++ sample: int main() {     std::cout << template_1() << '\n';     return 1;      } Every moron who knows C++ would know what this means. Now consider that almost every line is a regular expression, so try to translate it into your native language, English for example; line by line in steps. ... rofl lol oO? I tried to do that with the example and my head almost had a system shutdown.
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