I'd like to know your oppinion on this topic. (forgive me this core dump :-)
Programming games has always attracted me, but destiny ( = loosing three times an almost completed platform game in the CGA era, written in Turbo Pascal 3.0, together with the backup copies
) has made me work in a different sector of IT.
So now that it seems that I have more time I'd like to develop a game I've been thinking for many years now, but I find that there's so much info out there and so many ways of doing things that I keep falling into the classical "analysis paralisis" antipattern
In the "good old times" when you wanted paralax scrolling in the EGA there was basically one way of doing it quickly (for those who remember duke nukem - the non 3D version :-), and there was one fast flood-fill algo and there was one way of dealing with com ports; if you wanted wolfenstein, you did ray casting, if you wanted quake, you did BSPs.
But now I find myself spending more and more time reading and reading than coding or designing. And the problem is that usually there are pros and cons to every aspect of coding, so in the end I usually end with much more information, but finally with no objective clue as to which way to go :-) "UDP vs TCP", "Java3D vs JOAL vs ... ", "DirectX vs OpenGL", etc.. endless discussions come to mind. And finally I take a decision based on "gut feeling" which is probably the very same thing I could have done at the beginning without reading so much. I mean, an "informed gut-feeling decision" doesn't look better to me than a "plain-old-style gut-feeling decision".
Does anyone have similar feelings? How do you cope with them? Where do you place your threshold for stopping reading and start coding?