Aestu wrote:
dek wrote:
Big IT shop - Team fractures into multiple teams by subject matter and/or technology, and only meet and coordinate when the two areas overlap on a given project. Analysts are expected to keep things on the same page, but they are often only moderately technically inclined so they can only do so much. Ideas for technical optimization generally generate from within the development team and might actually make sense, but content decisions are made by people who have degrees in marketing and wear suits and use words like "synergize" and "market share" and generally have no fucking clue what they're talking about. There is created a subclass of IT employee that dreams of making it into development but is relegated to menial things like updating wikis. No one really gives a shit what they do and they are generally not managed in any meaningful sense.
Meanwhile, in the real world, PR is taken seriously by major corporations, and they spend millions on influencing the minds of consumers.
You yourself are proof of their success.
You do know I work in IT, right? And I work for a major corporation, and have worked for other major corporations as well as small IT shops in the past. I've also worked for a game company (EA Sports). I'm not telling this from the outside (like you are), I'm telling you what happens at work in every big shop I've worked in, and it was especially true at EA.
For example, you might think that the game works a certain way because someone decided that it should be so. Whereas I have seen, first hand, gameplay decisions made because the developer was under a quickly approaching deadline and decided that the current iteration of the code was "right", even if it didn't exactly meet the requirements.
Do you know what a "known shippable" bug is? That's where the dev team knows something is broken but ships the product anyways because they figure it's either obscure enough that it won't cause a problem or it's minor enough that it will be a constant annoyance for the gamers but not enough to make them stop. Or, it is also something you would decide was planned to be that way, even though it was in fact a bug in the code that they didn't have time to fix.
You see precision and carefully made decisions where the truth is a mixture of happenstance, miscommunication, or buggy software.

Akina: bitch I will stab you in the face