Instead of the internet, I lurked around the local library for game magazines with source code listings in the back.
I love this. I did the exact same thing at my local library looking for books on BASIC (now I lurk on HN instead of at the library). I always had trouble getting the code listings to work because they were usually written for a slightly different version of BASIC than what I had. Without the internet there wasn't really any way for me to figure out what the problem was so there was plenty of trial and error.
One of my best memories was finally buying Tricks of the Game Programming Gurus by Andre LaMothe. I remember reading almost the whole book the first day I got it and trying out all the great code examples. This was the first time I really saw how real games were made. It basically runs though making a game like Wolfenstein 3D only two years after it was released. I think it would be a struggle to write a book about how to make a triple A title from 2010.
Near the end of high school I stopped coding but when I got back into it several years later, I was amazed at the resources and tools freely available on the internet.
Looks good. I haven't heard of Speechhub but I look forward to your tutorial.
I recently added a blog to my static GitHub page using Jekyll (http://atomyard.com/blog/Blogging-with-Jekyll/). I found Jekyll to be very easy to use (and it's built right into GitHub) so I'd be interested to see how Speechhub compares.
That’s a fair point. However, there could also be front loading in the business role. Sounding out the market, figuring out who your customers are and what they want - the sort of stuff that should be done before writing any code. Isn't that still a significant amount of work?
I used to be of the opinion that the technical people did all the hard work and hence they should get the majority of the equity. However, once I tried to do everything myself I realised that the technical side was only one piece of the puzzle.
Business, design and marketing may not be as intellectual as programming but they are no less hard and often more important.
I really think that if two people are involved, the equity split should be 50/50 regardless of the skill set each one brings. If the equity is unbalanced, the level of effort each founder brings will be too.
There is also an interesting podcast on the process: http://theamphour.com/the-amp-hour-113-sudden-sinoamerican-s...