With all due respect, this is poop. I would never say that I don't care about community input. Maybe artists or writers can get away with delivering on a vision without outside input, but I don't believe many game developers can work that way, at least if they are building games with a large player base.
On the contrary, I recognized really early on in my career how valuable getting unfiltered feedback is from players. That's why I have always spent so much effort to try to communicate on forums, twitter or even face to face. I don't know how you can develop games without that input, and the fact that Riot takes player feedback so seriously is one of the reasons I decided it would be a good fit for me.
Now, it's possible that someone was misquoting or misremembering an instance when I was trying to explain the role of a game designer. Sometimes players will assert that the community should be responsible for balance (or even all) changes to a game, because players as a collective spend far more time with the game than any individual developer ever could. My opinion on that approach is that it wouldn't work well. Crowdsourcing is great at solving problems or even coming up with novel ideas, but it isn't great at designing things. Players have different interests or goals or even different visions for how they think a game should work. Instead, I believe better results are achieved when there is a vision holder making decisions, but those decisions are informed from player feedback.
The distinction is something like this:
-- Should a developer make *every* change suggested by players? No way and yikes.
-- Should a developer make changes that are informed by player feedback? *Every* time.