Comment by tmountain

Taking ClarityCorp as an example, I see an opportunity to focus more on the design phase (testing ideas) than the implementation phase. As engineers, we often dive directly into coding and implementing systems related to our problem rather than asking simple questions like, "is the game loop fun?" I've seen some brutally simple prototypes (150 lines of JavaScript) that represent an idea well enough to determine whether the idea has the potential to merit the time investment required to bring it to fruition. Personally, I'd rather test 15-20 different concepts at the lowest fidelity before settling on a direction than 2-3 half built games over the course of a year. Not knocking the author at all (kudos for producing some work). Just offering suggestions.