Totally fine with the feedback. Thanks for checking us out! To address your point though, we've actually found that we have a pretty awesome mix of users that consists of both early adopters and more "normal" people. For example, my dad loves movies and gadgets but never reads any tech blogs or hears about this stuff normally. He likes using our site because he can hear about things he is interested in but normally never wouldn't have been exposed to. But again, thanks for the feedback; user acquisition is obviously always an issue.
That was not the point at all. Criticism is totally fine and often valid, and it certainly aids in improvement. The point I was trying to make is that people are quick to criticize, but slow to compliment. We share our honest opinions when they're negative but not nearly as often when we have something positive to say.
I'm always open to criticism and am willing to improve. Sorry if that wasn't clear enough in the post.
The only downside I could see to this would be people freaking out because it would seem like Facebook is "tracking" them on their phones all the time. But I think it would be super useful if you did ever have your phone stolen.
That's a really interesting point. So maybe we're likely to comment on something positive that far exceeds the normal experience, but not say anything where "good" is already expected. I'd never thought of it like that.
Agree 100% with the college entrepreneurship club comment. The connections I made with entrepreneurial-minded, passionate people while still in school have been hugely beneficial.
Great article. I think most developers would jump at the chance to be more involved in "the process"; that is, working hand-in-hand with designers and not just being given some set of specs to whip up. The more mistakes you make, the more you learn. Plus, getting products or features into the hands of users gives you more valuable feedback than any amount of meeting-room discussion ever could.
I feel like the biggest danger with a system like this is that you might lose focus or passion while you're in between waves. Even if you're passionate about something while you're working on it, it seems like it would be very easy to become complacent working at your "in-between" job and difficult to get back working on your idea.
I think the very last point is one of the most important. The ability to drive users who are bored with the current game towards other, similarly addictive games is huge. The more games you can get one user to sink time into, the more money you can make.
While I can respect what the author is saying, I don't think everyone should follow this advice. While I've definitely had my fair share of time spent in the "shed", working on projects for both school and my own side ideas, I don't think a true college experience can be had by being like this all the time. There is nothing wrong with occasionally being distracted by your peers; I've had lots of great nights going out for a couple drinks on a Wednesday night just because I can.
In the end, it all has to be about balance in my opinion. Definitely go (far) above the bare minimum, but I know I could never stay sane without the occasional break or fun night out.
I don't really know why, but I always listen to some 90's music when I code. Third Eye Blind, Barenaked Ladies, Goo Goo Dolls, things like that.I just get in the zone when I have a good 90's playlist going on Pandora.