You are viewing a single comment's thread.

view the rest of the comments →


[–] smashinglyAwesome 0 points 22 points (+22|-0) ago  (edited ago)

its not a requirement but it would help if the developer is a gamer. he/she will know what the customer will like. if the developer is not gamer, we could have someone just cashing in a quick buck, business people making it all about the business ala EA style (we have 1 year 20 million buget how can we make the optimal game for a 200% profit). as a customer, i would be more inclined to buy the game knowing the developer is passionate about it.


[–] shinjukuthief 1 points 8 points (+9|-1) ago 

I'm going to point out that at no point did he say he doesn't play games. He is trying to define the difference between developing a game and playing the game. It may help if he had explained that gamers primarily play games and developers create games (not to the exclusion of playing games). If you pay attention to what he says instead of getting caught up in the words used in one sentence much of what he talks about is wanting to provide more open and honest information on how games are developed. So that gamers have a better understanding of the work involved. I don't agree with everything he says about the customer base, but he has some interesting points.


[–] ThirdSphere 0 points 5 points (+5|-0) ago 

I agree, I think a lot of the people commenting in this thread didn't watch the video. OP took that quote out of context; within the first minute he said "gamers and developers are separate things, and you can love games without calling yourself a gamer"


[–] MarianOnEarth 0 points 1 points (+1|-0) ago 

I agree with your analysis, but man does he come off as sounding douchy. Even the customer refund idea. Think of a store in the wild, and you get that one customer that just wants to be angry. "The cheeseburger has cheese! Let me speak to your manager" "This is too expensive. I'm not paying for it!" What I think he's trying to say is that the customer is always right model isn't always the best. Sometimes you have to kick someone out of your store.


[–] fluffingtonthefifth 3 points 1 points (+4|-3) ago 

Ya, of course, I just don't buy that a game necessarily has to be created by a gamer. The scorn and derision that Rami's opinion has garnered in some circles strikes me as more of a knee-jerk reaction than a considered response.


[–] Bazrum 0 points 4 points (+4|-0) ago  (edited ago)

I think the knee jerk reaction has more to to with the fact that he's an indie Dev. Typically indie devs and indie studios are much smaller, with a small team and not a whole lot of wiggle room.

With such a small team most of those people, if not all of them, should be very very immersed and knowlegable about games and how they work. It's nessisary that every single person on your team has at least a bit of gaming experience, otherwise you open up your studio to weaknesses that wouldn't happen with gamers at the helm. Bad choices in development can bring your game to it's knees well before launch.

Imo, if your Dev team (or at least the head of the team/most visable person) has someone who doesn't see themselves as a gamer it's going to be a lot harder for me to trust your game. It doesn't make me want to hear you out about the game and it makes the devs seem pretentious and like they're alienating their audience. How do I know this person knows what makes a good game, if they don't identify as a gamer? How can I leave the gaming industry's future to someone who doesn't care about gaming?

Saying something like "I'm not a gamer, now trust me I know how to make games" is not reassuring nor does it make a connection between Dev and gamer. It leaves a hole where usually there's a relationship formed, a bond that is the knowlege that both sides are gamers.


[–] lagadu 0 points 0 points (+0|-0) ago  (edited ago)

he/she will know what the customer will like.

That's not a developer's job, it's the product owner's. It's literally what that role exists for.