AmstradHero wrote...
In a word? Yes.Danny Boy 7 wrote...
I don't see how they're agreeing with you is relevant though. Does lack of experience in a field preclude true dev status? Sorry if I'm getting snippy I don't mean to. My uncle was in the army, he never fired a rifle, never uses the jargen when talking with me or my cousin's husband, yet we don't think he's NOT a soldier because his job wasn't one that we or the general ranks were involved in, nor do I call the men guiding our ships in or filing papers civilians because they haven't been in combat. They just either haven't had the chance or there skill set don't require them to leave.
If you haven't done something and don't understand the in-and-outs of the practical application of the knowledge, it is very difficult to make an accurate comment on how things work. To quote: "In theory, theory and practice are the same. In practice, they are not."
If you've never fired a rifle, you're not a combat soldier. You might serve in the army, but you're not qualified to talk about what it is like to be on the battlefiled. You might know about the tactics involved at a macro level and strategy and logistics, but you have not a whit of understanding of what it's truly like to be in combat and being fired upon.
If you've never tried to balance and continually test a game to judge the appropriate power curve for a character to ensure a good challenge for players of different skill levels, then you don't understand how much time is involved and the complex relationships between the different factors at play.
This isn't to say that players can't necessarily make good assessments and criticism of a game, but the routinely simplistic suggestions of "just change this" overlook the complexities of a modern game and their mechanics, because players haven't delved into the field to understand all the effects that "simple" change would have.
Okay maybe I need to separate my arguments a bit here, because I'm doing a sh!te job of it.
I agree that players should not be directing devs in the process of their profession nor berate said dev in how easy their job is because they know jack about it. Non-devs can have some really good suggestions/assessments as you said I'm not arguing that point, they can have equally sh!te suggestions as well. No argument here and I can see why simplistic "just change this" threads are incredibly irritating, the same way someone saying that all the garbage man does is pick up the trash. It's turning hard work into a menial often smug remark that makes what they do less than what it is, which is hours of hard work for someone. Thats rude, ignorant and overall just demeaning to the person doing the job.
However Upsettingshorts and hoorayforicecream were making the assumption that only non-devs are making these stupid threads which is where I find an issue. Now I will admit that 80 percent of the threads are likely made by non-devs or even less (we don't know after all), which is not the issue, however the assumption that ONLY non-devs make them is shortsighted because a dev can still make a suggestion that is stupid because they might not have the experience with that departement, feature etc or the pressure/scheduling may be drastically different in their particular environement. Does that make them not a dev? If you're answer is no than you should be able to say that while not all devs likely make these inflammatory threads, it's silly to assume that they don't, because they could after all have done so and with the amount of studios and diversity of what it means to be a developer it's not like it's improbable. I just don't think they want to imagine that someone who goes through what they do would make a thread asking for something stupid or insensitive as what those simplistic threads suggest.





Retour en haut





