Just something to think about..
Having no knowledge of game development, its very likely that your GDD contains huge holes that you aren't even aware of, even with 4000 pages.
Even if you did have experience, its still very likely that it contains holes, and things that when actually implemented will turn out to suck.
My point is a GDD is typically nothing static, but a living document.
Its not a recipe that someone writes, gives to the studio, and they then implement.
Sure, there are studios that work kind of like that, (though YOU have to pay THEM) but the games they create tend to suck.
The whole notion of "I have a GDD and I want to sell it so someone can implement it" is a big misunderstanding of how game development actually works...
(and of how you create great products in general imo...)
Show differencesHistory of post edits
#4Olof Hedman
Posted 02 September 2012 - 03:08 AM
Just something to think about..
Having no knowledge of game development, its very likely that your GDD contains huge holes that you aren't even aware of, even with 4000 pages.
Even if you did have experience, its still very likely that it contains holes, and things that when actually implemented will turn out to suck.
A GDD is typically nothing static, but a living document.
Its not a recipe that someone writes, gives to the studio, and they then implement.
Sure, there are studios that work kind of like that, (though YOU have to pay THEM) but the games they create tend to suck.
The whole notion of "I have a GDD and I want to sell it so someone can implement it" is a big misunderstanding of how game development actually works...
(and of how you create great products in general imo...)
Having no knowledge of game development, its very likely that your GDD contains huge holes that you aren't even aware of, even with 4000 pages.
Even if you did have experience, its still very likely that it contains holes, and things that when actually implemented will turn out to suck.
A GDD is typically nothing static, but a living document.
Its not a recipe that someone writes, gives to the studio, and they then implement.
Sure, there are studios that work kind of like that, (though YOU have to pay THEM) but the games they create tend to suck.
The whole notion of "I have a GDD and I want to sell it so someone can implement it" is a big misunderstanding of how game development actually works...
(and of how you create great products in general imo...)
#3Olof Hedman
Posted 02 September 2012 - 03:03 AM
Just something to think about..
Having no knowledge of game development, its very likely that your GDD contains huge holes that you aren't even aware of, even with 4000 pages.
Even if you did have experience, its still very likely that it contains holes, and things that when actually implemented will turn out to suck.
A GDD is typically nothing static, but a living document.
Its not a recipe that someone writes, gives to the studio, and they then implement.
Sure, there are studios that work kind of like that, (though YOU have to pay THEM) but the games they create tend to suck.
The whole notion of "I have a GDD and I want to sell it so someone can implement it" is a big misunderstanding of how game development actually works... (and of how you lead a team to create great products in general imo...)
Having no knowledge of game development, its very likely that your GDD contains huge holes that you aren't even aware of, even with 4000 pages.
Even if you did have experience, its still very likely that it contains holes, and things that when actually implemented will turn out to suck.
A GDD is typically nothing static, but a living document.
Its not a recipe that someone writes, gives to the studio, and they then implement.
Sure, there are studios that work kind of like that, (though YOU have to pay THEM) but the games they create tend to suck.
The whole notion of "I have a GDD and I want to sell it so someone can implement it" is a big misunderstanding of how game development actually works... (and of how you lead a team to create great products in general imo...)
#2Olof Hedman
Posted 02 September 2012 - 02:48 AM
Just something to think about..
Having no knowledge of game development, its very likely that your GDD contains huge holes that you aren't even aware of, even with 4000 pages.
Even if you did have experience, its still very likely that it contains holes, and things that when actually implemented will turn out to suck.
A GDD is typically nothing static, but a living document.
Its not a recipe that someone writes, gives to the studio, and they then implement.
Sure, there are studios that work kind of like that, (though YOU have to pay THEM) but the games they create tend to suck.
The whole notion of "I have a GDD and I want to sell it so someone can implement it" is a big misunderstanding of how game development actually works...
Having no knowledge of game development, its very likely that your GDD contains huge holes that you aren't even aware of, even with 4000 pages.
Even if you did have experience, its still very likely that it contains holes, and things that when actually implemented will turn out to suck.
A GDD is typically nothing static, but a living document.
Its not a recipe that someone writes, gives to the studio, and they then implement.
Sure, there are studios that work kind of like that, (though YOU have to pay THEM) but the games they create tend to suck.
The whole notion of "I have a GDD and I want to sell it so someone can implement it" is a big misunderstanding of how game development actually works...
#1Olof Hedman
Posted 02 September 2012 - 02:47 AM
Just something to think about..
Having no knowledge of game development, its very likely that your GDD contains huge holes that you aren't even aware of, even with 4000 pages.
Even if you did have experience, its still very likely that it contains holes, and things that when actually implemented will turn out to suck.
A GDD is typically nothing static, but a living document.
Its not a recipe that someone writes, gives to the studio, and they then implement.
Sure, there are studios that work kind of like that, but the games they create tend to suck.
The whole notion of "I have a GDD and I want to sell it so someone can implement it" is a big misunderstanding of how game development actually works...
Having no knowledge of game development, its very likely that your GDD contains huge holes that you aren't even aware of, even with 4000 pages.
Even if you did have experience, its still very likely that it contains holes, and things that when actually implemented will turn out to suck.
A GDD is typically nothing static, but a living document.
Its not a recipe that someone writes, gives to the studio, and they then implement.
Sure, there are studios that work kind of like that, but the games they create tend to suck.
The whole notion of "I have a GDD and I want to sell it so someone can implement it" is a big misunderstanding of how game development actually works...