Quote: "Quote: "I help you with few classic reasons :
1 - lack of time hummmf you're reading this thread right now no ? :p
2 - i have a family ... the same as everyone
3 - my job takes a lot of time (see pt 1 & pt 2)
4 - Motivation ? the AppGameKit Community is here to help you maybe ?
5 - i have lost the source code of my game (ok ok...)
And you ? :p why don't you release some games ?"
"
I have a fairly unique(?) situation.
I don't make games for money or need to.
I don't have a schedule or set timeline for finishing anything
I don't mind if I don't finish something, although I would rather do so.
I treat this whole experience as a long term (or even never ending) project, whereby if something comes out the other end, then it's a bonus. There's no pressure.
I've had kids, they've grown up and left home. I don't watch TV. I have increasing amounts of spare time.
Having worked on some incredibly huge projects in my time (e.g. 10 million lines of code,45 man year projects etc.) I know it's sometimes a slog. A lot of people go through phases during developments; they prototype nice shiny things, but sometimes realise that the relative drudgery of making menus and stuff is boring - as is writing sensible, re-usable code that can be looked at 3 months later without feeling like poking your own eyes out.
They also don't know about certain design principles which help in developing reasonable sized pieces of work, e.g. state machines and struggle to reinvent the wheel and therefore get disillusioned.
My son actually pointed out to me about 15 years ago - "dad, you never actually finish any of these games".. I agreed. I used to like the early prototyping of effects and getting a feel of what something may turn into. The real skill and labour comes with the finishing; the final touches and the completion. Not everyone has those skills.
This is why solo game development is hard. The belbin scale describes the ideal skillset when assembling a team. If you are familiar with this, it includes ideas people and completer/finishers as usually mutually exclusive - these are rarely the same person.
A solo dev who gets a good idea, implements and finishes is a rare thing indeed .