Slashdot Mirror
EA Games: The Human Story
An anonymous reader writes "An Electronic Arts employee spouse speaks out against company crunch time practices. From the post: "EA's bright and shiny new corporate trademark is "Challenge Everything." Where this applies is not exactly clear. Churning out one licensed football game after another doesn't sound like challenging much of anything to me; it sounds like a money farm. To any EA executive that happens to read this, I have a good challenge for you: how about safe and sane labor practices for the people on whose backs you walk for your millions?"
EA's bright and shiny new corporate trademark is "Challenge Everything." Where this applies is not exactly clear. Churning out one licensed football game after another doesn't sound like challenging much of anything to me; it sounds like a money farm. To any EA executive that happens to read this, I have a good challenge for you: how about safe and sane labor practices for the people on whose backs you walk for your millions?
I am retaining some anonymity here because I have no illusions about what the consequences would be for my family if I was explicit. However, I also feel no impetus to shy away from sharing our story, because I know that it is too common to stick out among those of the thousands of engineers, artists, and designers that EA employs.
Our adventures with Electronic Arts began less than a year ago. The small game studio that my partner worked for collapsed as a result of foul play on the part of a big publisher -- another common story. Electronic Arts offered a job, the salary was right and the benefits were good, so my SO took it. I remember that they asked him in one of the interviews: "how do you feel about working long hours?" It's just a part of the game industry -- few studios can avoid a crunch as deadlines loom, so we thought nothing of it. When asked for specifics about what "working long hours" meant, the interviewers coughed and glossed on to the next question; now we know why.
Within weeks production had accelerated into a 'mild' crunch: eight hours six days a week. Not bad. Months remained until any real crunch would start, and the team was told that this "pre-crunch" was to prevent a big crunch toward the end; at this point any other need for a crunch seemed unlikely, as the project was dead on schedule. I don't know how many of the developers bought EA's explanation for the extended hours; we were new and naive so we did. The producers even set a deadline; they gave a specific date for the end of the crunch, which was still months away from the title's shipping date, so it seemed safe. That date came and went. And went, and went. When the next news came it was not about a reprieve; it was another acceleration: twelve hours six days a week, 9am to 10pm.
Weeks passed. Again the producers had given a termination date on this crunch that again they failed. Throughout this period the project remained on schedule. The long hours started to take its toll on the team; people grew irritable and some started to get ill. People dropped out in droves for a couple of days at a time, but then the team seemed to reach equilibrium again and they plowed ahead. The managers stopped even talking about a day when the hours would go back to normal.
Now, it seems, is the "real" crunch, the one that the producers of this title so wisely prepared their team for by running them into the ground ahead of time. The current mandatory hours are 9am to 10pm -- seven days a week -- with the occasional Saturday evening off for good behavior (at 6:30pm). This averages out to an eighty-five hour work week. Complaints that these once more extended hours combined with the team's existing fatigue would result in a greater number of mistakes made and an even greater amount of wasted energy were ignored.
The stress is taking its toll. After a certain number of hours spent working the eyes start to lose focus; after a certain number of weeks with only one day off fatigue starts to accrue and accumulate exponentially. There is a reason why there are two days in a weekend -- bad things happen to one's physical, emotional, and mental health if these days are cut short. The team is rapidly beginning to introduce as many flaws as they are removing.
And the kicker: for the honor of this treatment EA salaried employees receive a) no overtime; b) no compensation time! ('comp' time is the equalization of time off for overtime -- any hours spent during a crunch accrue into days off a
Cause every programmer at one point or another wants to make video games. Don't like your job? Leave... there are 500 people that want to be in your place, anyway!
That's why most of the industry is young. Us 'older people' with families realize that they can't be in the gaming industry. I have a wife, kid, and another kid on the way. I'm not about to sacrifice my family so that I can work on video games. Sure, it was a dream of mine, but that's what the industry is about. Long hours, low pay, no pats on the back. If you don't like it, there is hundreds willing to take your spot.
Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
I've come to accept perpetual crunch time, unpaid overtime, and no comp days as "industry standard."
I guess that makes me part of the problem. Reading this article woke me up a little... maybe I should be getting those things. I wonder how many programmers are in the situation of having little to no 'crunch time' and paid overtime and comp days? Especially paid overtime -- who gets that? Anyone?
A. Incompetant management. No new story here, and we've all suffered under it.
:)
B. Outsource the whiners to a country where, at least if they do whine, no one here will hear them. Also something many of us have lived through.
No, they aren't going to outsource management but thanks for the suggestion. In my experience, that's like throwing gasoline on a fire. You think the bastards in *this* country are greedy incompetants, wait till you see some of the lads and lasses Over There.
Simple solution? Don't do it. At one point in my career I was good enough at fomenting revolts that even the Indian and Russian contractors joined in. The key is to pick the part of the deathmarch where hanging management actually sounds like a reasonable solution. A few weeks of 12-hour days, seven days a week makes any way out welcome.
Rb
AFAIK you cannot be forced to work overtime. Thus employees could have said no. If there we dismissed then that would be grounds for a law suit. EA may treat their employees poorly but it seems that the employees treat themselves just as poorly. Stand up for yourselves.
UNIX/Linux Consulting
Call me lazy but working 80 hours of week while only getting paid for 40 is just stupid exploitation in my book.
Now I live in the EU where it's mostly against the law to make me work more than 40 hours a week without paying me for it. Of course I still work probably 50-60 hour weeks. Atleast it's my choise now and if I want to slow down I can.
--Smutt
The Information Revolution will be fought on the command line.
No, ninety hour weeks are NOT an inevitable consequence of working in this industry.
45-50 hours, maybe. But >80 hour workweeks are usually seen only at startups where if a major deadline is missed, the company fails. And in those cases, the people put up with it because there's usually more than just a wage involved--working long hours at a startup can make you millions in the end.
Established companies pushing their staff that hard is not only morally wrong, it's bad business. Sure, EA makes a lot of money, but how much more could they make if they didn't have such high turnover?
Here's a news flash: Humane labor practices != socialism. Jackass.
http://www.bradheintz.com/
- updated
I was wondering, if EA is engaged in breaking the law, and nobody does anything about it and the government doesn't seem to care, should software engineers unionize?
Think about it, if there are the screen actors unions and contruction worker unions, why can't there be Software Engineer Unions?
Maybe then we can make sure to work 40-hour weeks with extra pay. Maybe then will Project Managers put on themselves realistic expectations, maybe then will CEOs learn that software making is a profession as valuable as business management.
I lived through something like this myself during the first internet boom. I worked over-100-hour weeks every week of the year. I still remember having spent two new year eves working. All I had was two weeks of vacation a year which I had to take in one-week instances, and having provided a two-month advance notice.
I was not paid overtime, weekends, or holidays. I did it because I was young, naive, and trully excited about what I was doing, but when I think back I was definitelly exploited along with my fellow co-workers.
In the end I started my own company and moved to a country with better work practices. Let's only hope that those still toiling for the further advance of computer science get a better deal soon. Uninioze and I'll go back and join you. I know what you're going thru, and I will do all I can to support you.
I've worked at 3 different game companies, including EA. EA is the absolute worst for crunch time. I, along with most of my team, worked every single day for 4 months straight, 80+ hours a week, and were told by management that we had it easy (other teams had had mandatory Saturdays for a whole year). After crunch time was done, I mentioned my concerns about the overtime to management. This led to my being placed on a probationary "get your act together" period, one step away from being fired. Knowing that life could be so much better, I quit.
Old people fall. Young people spring. Rich people summer and winter.
I worked in the game industry for a year and 1/2. In that time I worked on 3 projects, and was always in cruch. I averaged over 75 hours a week for that year and 1/2 period. Some weeks I spent over 120 hours in the office.
Bad management, unrealistic schedules, artificial deadlines, I've seen it all while deathmarching. And the end product was always rushed out the door before it was ready..... so it was junk. The company killed a lot of previosly sucessful franchises by pushing junk, in order to meet financial obligations. There were controlled by their debt, not by any desire to produce a quality game.
Thankfully the company I worked for is now bankrupt, and hopefully dead.
Fly Fish? Participate in our forum
Not really!
As you work more hours, the mistakes rise. A company would be better off getting 40 or 50 great hours instead of 80 or 90 mediocre to poor hours.
This also may burn out the people who have been there longer, so a lot of the team might be younger and more inexperienced.
Also, if this keeps up long enough, I wonder if the peons might consider unionizing. I have seen the abuse of unions, and it is not pretty. When a union gets too powerful, bad thing happen. But, obviously, in a case like this, a disposable work force means that management makes bad things happen.
But here are a couple of practical idea:
1) Contact the Department of Labor. They have investigators who look into such things. I know -- I have a relative who does this for a living.
2) Take a job coding a database, or become a sysadmin, or so anything else. Maybe a little less money, a little less glamor, but you actually get to know those people who live in your house. Then, you can code games in your spare time (spare time - what a concept), where you can enjoy it at your own pace.
The reason that companies work people 80 hours a week is that they CAN. If everybody refused to work these hours, it would hurt. You might get fired. But if EA had such a huge turnover of staff that they could not finish ANY project, they might change their ways.
Just my $0.02. From an engineer who works a fair amount of 40-hour-weeks.
"-1 Troll" is the apparently the same as "-1 I disagree with you."
so I hope the spouse's question about the CEO's pay was rhetorical, since it must be disclosed by EA. He makes $1.45 million per year, but last year alone he made $22 million through stock option sales.
The CEO and most everyone else seems to do nothing but sell his stock at every opportunity. They have more insider activity than most huge companies. Interesting.
My advice: if you don't agree with EA practices, dont buy any of their products. Hit them where it hurts, and if they lay people off, you're doing those workers a favor anyhow.
A year spent in artificial intelligence is enough to make one believe in God.
Did you even read the post or just glean your idea from skimming it?
What upsets is that someone complains about unfair labor practices and you cry out quit, stand in an unemployment line and label them a socialist. Just because there are a hundred other people that would take that job doesn't make the management's practices right. We work in an educated country and salary slavery is just as wrong as outright slavery.
I've worked those kinds of hours and I can honestly tell you it sucks. I continued on because I enjoyed my work, but it soon extracted its toll on my health and my family life. When I saw what it was doing to me, I left for a better job for less money but I work normal hours and have a life.
So before you start labeling people and puking in the unemployment line, think; there is a human side to a business and these types of work practices reflect bad managment and not a rise in socialism.
Really. I'm a veteran of the coding wars, and yes, death marches are nothing new. The tactic of the perennially slipping deadline ("whoops, heh heh, crunch mode just got extended 2 weeks, sorry") is the telltale sign of incompetent software management. (My SO had a similar experience in the telecomm industry before the big crash.) A German shepherd could figure out what's happening to this organization.
The team involved has to revolt unanimously -- somewhere a manager needs to get seriously bitch-slapped with some slippage. I'm not talking about sabotage, mind you; let's stay professional, even though noone will ever die as a result of EA's bugs. But what about having an entire department or two calling in sick on the exact same day?
It's the crudest form of organized labor, but it works. Just like the "blue flu" that hits US cities when the policemen's union protests conditions. And the larger and more critical the department involved, the better.
Yes, there is the risk of an en masse firing. On the other hand, if this article is true, what is there for the engineers to lose? Paychecks are nice, but health and sanity are rather nifty too.
--- The American Way of Life is not a birthright. Hell, it's not even sustainable.
Fuck That Place.
Seriously, it's a carrer choice.
I liked working as a field tech. Got to drive around, working on different people's problems. I loved helping people and getting to feel like a hero. I did not like the pay, or the, "Stay on site until it's done, but be here at 8:00 a.m. tomorrow" attitude. I quit after 1 year.
I liked working as a hosting admin. I dug servers, and working with the OS to do the developers bidding. I did NOT like getting paged constantly with servers issues that were beyond my control due to the crappy product. I quit after 2 years.
Now I am a programmer, and I currently like where I am. The whole time I have had a family to support, but I know if I am not happy at work, nobody is going to be happy at home. I bet the guy shoveling shit at the horsetrack doesn't like his job either, he should quit too. That's the great thing about America, you can just go get a new job. Sure you may have to give things up, but a job is all about choice.
You have to decide what is important to you. You will never be rich as a teacher, but be a teacher if it's what you love. You will never (I guess from this article) be rich as a game programmer, or have a life outside of work, but you get to do what you love. I play a lot of poker, and toyed with the idea of going pro, but after a very short try (kept my job, just played at the pro level for a few weeks), I really did not want to play poker.. at all! It became a job.. a job I wanted to quit.
So, pick a job you like. Some people LIKE having a job that is their life, some people like having a hobby that turns into a job. The whole of the job is equal to the sum of all it's parts.
Modest doubt is called the beacon of the wise - William Shakespeare
I think the big question is, how can we get small game studios back? Is it really not possible for a small team to make commercial games? I'm sure a lot of game developers (programmers, artists etc.) would work for a lower salary at a nicer place. And I deeply believe better games would be coming out of a smaller and more laid back studio, though perhaps not as often.
Yes, I can see where this fails, the money. But surely there must be a way to change the current development? The game market seems bigger than ever, do people really only care for the huuge games made by EA & co?
Martin
I've worked in the Video Games industry for just under 20 years (first game published in 1985). The last company I worked for expected 50-60 hour work weeks -- several people were fired from there for not working the mandatory extra 10-20 hours a week as "slackers". They scheduled me on one project where I had to convert 400,000 lines of assembler in 4 months. That's about 3,000 lines of code a day, converted and debugged. I managed to do it by working 100 hour weeks with 16-20 hour days for four months. My health was so bad at the end of the project I nearly had a liver failure from an infection that a healthy immune system would have easily fought off.
The company I currently work at had us working nights and weekends to finish projects and during crunch (the last project had an 8 month crunch!) many team members were working around 70-80 hours a week. Unfortunately, successes under crunches like these tell upper management that it's a good thing to work employees under heavy hours and a high workload situations.
Due to lobbied labor laws that prevent salaried software engineers from receiving overtime pay, the industry has taken this as a "pay a set fee, work'em as hard as you can" attitude. If they double the hours worked, they halve their perceived cost per man hour.
Not surprisingly, burn out rate and job-hopping are really high in the games industry. Too bad it's pretty much the same at nearly all video game companies that I know. Mandatory nights and weekends leave little personal time for any software developers -- especially commuters or employees with families.
Oh well, at least the team I'm on has a big enough title that when the royalties come in, we'll make a decent wage per hour, but if you're on a smaller title or working without royalties, you might make less per hour than a Walmart manager if you go into video games programming.
My advice: if you don't agree with EA practices, dont buy any of their products. Hit them where it hurts, and if they lay people off, you're doing those workers a favor anyhow.
That's practical advise, in a sense, because if their "brand" turns sour (like Gator), then EA shareholders are in trouble.
The impracticallity is that most of the market are too young to care or be informed about labour practices.
If EA is really breaking the law, then a lawyer should approach any EA employees for the purporses of a class action suit. That would get their attention, and maybe there'd be some real change.
Like all pain, suffering is a signal that something isn't right
Quoteth mad.frog: "Shortly after I left EA, I happened to meet someone who has just started at EA-Maxis. I tried to diplomatically warn him that things could get unpleasant, but he reassured me that he knew what he was doing. One year later, he contacted me asking if my current employer was looking for help, as he had to quit -- similar conditions had destroyed his life (and cost him a girlfriend, as well)."
:-)
I'm that friend, and yes he warned me. The games industry has always been this way, and I worked at other games and film companies (you know, the one that did Toy Story). I thought I knew what to expect going in, but EA is by far the worst digital entertainment company in terms of how they treat their people. Its really ironic that their HR tag line is "The Number One People Company". They mean: Number one people burn out company. There are many stories here, but the one that really stands out was that my manager had to quit the games industry FOREVER under doctor's orders. He had uncontrollable back spasms due to work stress. Years of this sort of mandated hell will do that to a person.
Add to this irony that I worked on a game that gave people "a life". My goodness, my own life was taken away so that I could make a video game that essentially took the players lives away since you had to sit in front of a TV for hours to get this fantasy life.
I've seen the posts that say "Just Quit". Well I did, but its very hard to do on the spot since it is your means of income at the time. You also get very close to your team members since you band together to try and get your product out the door. Heck you're also all depressed, stressed, and sick at the same time, so there are many levels to bonding going on.
I've never been a fan of unions, but in this case the employees at EA need to think about it. The hours are insane, and so are the expectations. It comes with the territory though.
As mad.frog said to me, "You've been warned". I'm saying the same to everyone else.
By now, we've all read that cathartic LiveJournal entry (or the reposting here on slashdot) by an angry EA widow who has had her husband, her family life, and her own career co-opted by the hellish product development environment that has become the norm at Electronic Arts. Most of us in the business know, right down deep in our ulcers and migraines, exactly what she's talking about. Too many of us have been caught in "normal" development cycles that require overtime as a matter of course; and have been at the mercy of abusive managers who ratcheted us up to several months of 13-hour-a-day/7-day work weeks. Perversely, these managers always claim that this is what's required to make the schedule - and (the mendacity of this part is always breathtaking) to prevent our work hours from expanding even more in the future.
i ves/2004/11/11/643#more-643
These stories are nothing new to me. I spent my 20s living them - and my 30s figuring out how to avoid ever doing that again.
Let me begin by establishing my bona fides. I've been building software for more than 20 years. Fifteen of those years were in the games business; half of those years were spent at EA's Bay Area offices as an external developer and an employee. I've held just about every technical position from tool programmer to director of engineering. As a programmer I've worked by myself and on teams of almost a hundred engineers. As a manager at a Fortune 100 company (Adobe) and elsewhere, I ran teams of up to 25 people, working on up to five projects at once. I've managed multi-million dollar art-intensive games, single developers, and core technology teams responsible to as many as eight clients (all with different requirements and all on different shipping schedules). Over the course of my career, I've been "in charge" (i.e. the senior engineering or project manager) on more than a half-dozen published titles, and held up the technical direction or project management end on over two dozen more.
In all that time, for all those titles, no project I was in charge of has ever missed its ship date or overshot its budget.
Yet I absolutely refuse to work the kind of death march hours ea_spouse describes. And I have never, ever asked or allowed my employees to do so.
Her story - and others that have been shared in the industry-wide conversation that her post provoked - make it clear that EA's management believes, as a matter of institutional principle, that only way to make money at games software is to create tight schedules, and the only way to make a tight schedule is to work your employees harder.
Decades of software engineering research and best practices - and my own experience - prove conclusively that this belief is complete bullshit.
Read the rest at: http://enginesofmischief.com/blogs/ramblings/arch