19 karma · joined September 17, 2009
Right now, in Kansas City you have one provider with no reviews, so for me it has not yet solved the problem, but it is a great start!
One important difference though: Like another commenter said, I am not as eager to accept any investor terms thrown my way, nor am I gauging my success on investor interest. I am in this to make a profitable, successful business venture, and will only accept investment on good terms when it will directly aid in the growth of my company. Perhaps that is why VCs might avoid older entrepreneurs, we are more cautious of investment deals, and don't judge success by those alone.
It is much like getting car repairs. If you go in informed, you are likely to get a fair price, whereas if you don't you may be taken advantage of.
Of course there is always the chance that this is deliberate, and done to make the story more sensationalistic, but I prefer to follow Hanlon's Razor: "Never attribute to malice that which can be adequately explained by stupidity."
The idea is based on a few aspects that game developers almost universally share: they are trained to think of new, innovative ways to solve problems since each new game has to push the boundaries of what was possible before, they tend to be passionate about development and doing cool things with code, they are hardcore about optimization, and they are used to constantly learning new technologies and algorithms.
That said, not all aspects of game development are ideal for other projects, especially on the web. As others have mentioned, web development requires a very different mindset than game development. One major example is that game developers often build components from scratch, rather than re-using existing ones. One of the hardest skill for me to learn was to avoid "reinventing the wheel" and using pre-made off the shelf and open source components in projects.
I am definitely biased, but my own experiences have caused me to pay more attention to resumes I get that list game development experience, but not to the point of excluding others.
As a coder who understands UXP but is not great with design, I often fall back on blues or grays for my projects. For whatever reason I find that designs I make tend to look better in blue than other colors. Reds too often look pink, oranges and yellows are hard to keep from looking overpowering. Greens aren't too bad, but I still have trouble getting it to look just "right." Maybe it is just me.
I don't like this regulation or think it is necessary, but it may actually do some good for the consumer.
We are struggling with this issue with my current startup, whether to do yearly or monthly only, or both, and what the comparative rates would be.
For new business and services online, the site or service should built with a business model in mind, even if it does not launch with one. And the best business model is simple -- find something people value and charge them a fair rate for it. The hard part is figuring out what that is.
The biggest problem with this design however is that it does not add anything to the experience other than aesthetics. In fact, it obscures many options and reduces usability. So how is this a power user's interface? Appearance is nice, but usability and understandability are much more important with design.