this thread does not want to be taken serious.
But it want you to think about yourself and your expectations.
All numbers are wild guesses :evilgrin:.
What are Game Development “Skills”
It is as simple as it sounds: Game Development Skills is the knowledge to create a game with the tools provided.
Skill level - Skill class
You see there is no 100% skill class. That is to leave space to the top. But feel free to tell everybody you have the 100%.
The typical game developer is starting with no clue, quickly increasing the first few skills and finally discovering the hidden secrets of game developing.
BTW. I’m writing game developing, not programming or modelling ;).
How to increase the skills?
- Develop games
- Contribute to games
- Follow tutorials
- Read Books about game development
- ask more or less intelligent questions + read the answers
- practice practice practice
Now the interesting part.
The “Skills - Project-Size” - Ratio
What does that mean.
The blue graph shows the skills of the developer as shown above.
The red graph shows the size of the project as the developer has planned it.
The green graph shows the size of projects he can handle with his skills.
According to our forum, 90% of the Noobs plan a game project that is simply HUGE. So we define HUGE as 100%. They start their project and discover a MMORPG + Next generation Graphics + BBQ on the GPU is a little bit to much as first project.
Suddenly they turn into Beginners. The project size drops down to something more realistic, but according to their skills still to much.
After failing a few projects they give up or turn into Intermediate. The projects size drops a bit more. The reason is simple … an Intermediate want to proof he is able create a game.
Welcome to the club of game creators .
At BlenderArtists.org a game creator should have at least one thread in the Finished Games forum. If not look at the projects of our heros!
Our heroes created a game and turned into Advanced. The next game project should be a bit more ambitious. Unfortunately the bit is a bit to much again. But the experience of that turns an Advanced to an Experienced.
The skills of the Experienced increased but the planned projects too. Luckily it is always possible to put slowed projects on hold and grap a new one. Team projects are quite promising at this time, as an experienced would not look lame anymore compared to others. A game developer should discovered his specialization as well.
Anyway the skills to judge your own abilities increases and the following project are much easier to complete. Now you are an Expert.
To discover the last level of skills you need time and practice and someone who calls you a “Guru”. A Guru has his own highly sophisticated, but he is clever enough not to tell everybody. While he is working on that he spreads his wisdom in this or that project always checking that it does not eat to much of his rare spare time. A Guru is pretty good in judging how long a project will take and if it has the potential to result in a finished Game.
(BTW. I’m not a guru :no:)
Why are there so less experts and gurus?
It takes a looooong time to come to this level. A lot of game developers give up at a certain level (mostly blaming the tools). Other change their live and loose interest in game creation. And some become Experts and Gurus but move to other communities.
The “Skills-Documentation” - Ratio
That are interesting charts. When looking at it keep an eye on the other one.
The project sizes increased with the skill level. Even we think we have a huge brain we can’t keep a full sized project in head (not if you need to remember what your girlfriend wishes for her birthday). Therefore it is recommended to write down your ideas = documentation.
For mysterious reasons nobody want to do that. I do not want to explain it because of the posts max character limit. It is 1000 Characters not 1000 pages. But to give this universe of reasons not to document anything a name … it is called lazyness. And I’m the emperor of it :evilgrin:.
Back to the chart.
Blue graph = skills again
red graph = the amount of documentation created relative to the
green graph the amount of documentation needed.
Green has a direct relationship to the project size. Finally even a Pong game should have a document that tells the user, what he should do, can do, who created it and how much it costs. Yes writing a user’s manual is part of the game development process.
Lets look at the graphs.
The Noob wants everything and wants to do nothing, not even writing down what he wants. Where is the “make my game”-button?
The Beginner starts with a small project and keeps everything in his head (on that size it seems to be fine) unfortunately a beginner can only distribute one copy of his game. Even a game developer has only one head to be bundled in the box. Luckily the project fails because the beginner forgot what he wanted to achieve. Typical case of missing documentation. Yes, writing down the requirements is part of the game development process. I do not talk about hardware requirement. Roasting chickens on the GPU should not be a requirement (for whatever reasons gamers it is).
The Intermediate finished the game with or without documentation. (Keep in mind the project size is small). Now he recognized users are crying for manuals, screenshot and videos. While sitting there and writing the manual the intermediate recognized it is nearly the same what he wrote an a napkin at the beginning of the project.
= Notice for the next project -> keep your design document.
The Advanced does exactly that, he writes an electronic version of the design document. Unfortunately he changes his mind in the middle of the project which invalidates all written documents. (No time for updates). Finally he has to write the user’s manual from scratch. That is not so bad as the Advanced discovered some design flaws that he needs to correct (which invalidates the new documents either).
The Experienced is clever he just digs through his chest of unfinished ideas and can present a design document within … half a day (depends if he can find the one from two years ago). If not it takes him one day to write a new one. The projects have a size that makes it impossible to change the design in the middle of the development. That keeps the Experienced head straight forward using the design document as his bible.
The Expert takes it easy he requests the design document from other developers. Then he changes it to fit his opinion. Luckily the Expert knows what documents are needed and what they should contain. Finally he writes a lot of documents to communicate with other team members or that he does not forget to replace all the cubes with real models.
The Guru writes Tutorials and Books not documentation. He might review the documentation of Experienced+. That is all you can get from a guru. A guru has to maintain his appearance of mysticism. Documents would destroy that.
BTW. A guru adds the Users manual to the game ;).
I hope you enjoyed reading this. Today I’m a bit ill. That’s why I have some silly? thoughts today.
If you have some comments post it here