Video game developer
|Part of a series on the:|
|Video game industry|
A video game developer is a software developer specializing in video game development – the process and related disciplines of creating video games. A game developer can range from one person who undertakes all tasks to a large business with employee responsibilities split between individual disciplines, such as programming, design, art, testing, etc. Most game development companies have video game publisher financial and usually marketing support. Self-funded developers are known as independent or indie developers and usually make indie games.
A developer may specialize in a certain video game console (such as Nintendo's Nintendo Switch, Microsoft's Xbox One, Sony's PlayStation 4), or may develop for a number of systems (including personal computers and mobile devices). Video game developers specialize in certain types of games (such as role-playing video games or first-person shooters). Some focus on porting games from one system to another, or translating games from one language to another. Less commonly, some do software development work in addition to games.
Most video game publishers maintain development studios (such as Electronic Arts's EA Canada, Square Enix's studios, Activision's Radical Entertainment, Nintendo EAD and Sony's Polyphony Digital and Naughty Dog). However, since publishing is still their primary activity they are generally described as "publishers" rather than "developers". Developers may be private as well (such as how Bungie was, the company which developed the Halo series exclusive to Microsoft's Xbox).
In the video game industry, a first-party developer is part of a company which manufactures a video game console and develops exclusively for it. First-party developers may use the name of the company itself (such as Nintendo), have a specific division name (such as Sony's Polyphony Digital) or have been an independent studio before being acquired by the console manufacturer (such as Rare or Naughty Dog). Whether by purchasing an independent studio or by founding a new team, the acquisition of a first-party developer involves a huge financial investment on the part of the console manufacturer, which is wasted if the developer fails to produce a hit game in a timely manner. However, using first-party developers saves the cost of having to make royalty payments on a game's profits. Current examples of first-party studios include SIE Worldwide Studios for Sony, and Xbox Game Studios for Microsoft.
Second-party developer is a colloquial term often used by gaming enthusiasts and media to describe game studios who take development contracts from platform holders and develop games exclusive to that platform, i.e. a non-owned developer making games for a first-party company. As a balance to not being able to release their game for other platforms, second-party developers are usually offered higher royalty rates than third-party developers. These studios may have exclusive publishing agreements (or other business relationships) with the platform holder, but maintain independence so upon completion or termination of their contracts are able to continue developing games for other publishers if they choose to. For example, while HAL Laboratory initially began developing games on personal computers like the MSX, they became one of the first second-party developers for Nintendo, developing exclusively for Nintendo's consoles starting with the Famicom.
A third-party developer may also publish games, or work for a video game publisher to develop a title. Both publisher and developer have considerable input in the game's design and content. However, the publisher's wishes generally override those of the developer.
The business arrangement between the developer and publisher is governed by a contract, which specifies a list of milestones intended to be delivered over a period of time. By updating its milestones, the publisher verifies that work is progressing quickly enough to meet its deadline and can direct the developer if the game is not meeting expectations. When each milestone is completed (and accepted), the publisher pays the developer an advance on royalties. Successful developers may maintain several teams working on different games for different publishers. Generally, however, third-party developers tend to be small, close-knit teams. Third-party game development is a volatile sector, since small developers may be dependent on income from a single publisher; one canceled game may be devastating to a small developer. Because of this, many small development companies are short-lived.
A common exit strategy for a successful video-game developer is to sell the company to a publisher, becoming an in-house developer. In-house development teams tend to have more freedom in the design and content of a game compared to third-party developers. One reason is that since the developers are employees of the publisher, their interests are aligned with those of the publisher; the publisher may spend less effort ensuring that the developer's decisions do not enrich the developer at the publisher's expense.
Activision in 1979 became the first third-party video game developer. When four Atari, Inc. programmers left the company following its sale to Warner Communications, partially over the lack of respect that the new management gave to programmers, they used their knowledge of how Atari VCS game cartridges were programmed to create their own games for the system, founding Activision in 1979 to sell these. Atari took legal action to try to block sale of these games, but the companies ultimately settled, with Activision agreeing to pay a portion of their sales as a license fee to Atari for developing for the console. This established the use of licensing fees as a model for third-party development that persists into the present. The licensing fee approach was further enforced by Nintendo when it decided to allow other third-party developers to make games for the Famicom console, setting a 30% licensing fee that covered game cartridge manufacturing costs and development fees. The 30% licensing fee for third-party developers has also persisted to the present, being a de facto rate used for most digital storefronts for third-party developers to offer their games on the platform.
In recent years, larger publishers have acquired several third-party developers. While these development teams are now technically "in-house", they often continue to operate in an autonomous manner (with their own culture and work practices). For example, Activision acquired Raven (1997); Neversoft (1999), which merged with Infinity Ward in 2014; Z-Axis (2001); Treyarch (2001); Luxoflux (2002); Shaba (2002); Infinity Ward (2003) and Vicarious Visions (2005). All these developers continue operating much as they did before acquisition, the primary differences being exclusivity and financial details. Publishers tend to be more forgiving of their own development teams going over budget (or missing deadlines) than third-party developers.
A developer may not be the primary entity creating a piece of software, usually providing an external software tool which helps organize (or use) information for the primary software product. Such tools may be a database, Voice over IP, or add-in interface software; this is also known as middleware. Examples of this include SpeedTree and Havoc.
Indie game developers
Independents are software developers which are not owned by (or dependent on) a single publisher. Some of these developers self-publish their games, relying on the Internet and word of mouth for publicity. Without the large marketing budgets of mainstream publishers, their products may receive less recognition than those of larger publishers such as Sony, Microsoft or Nintendo. With the advent of digital distribution of inexpensive games on game consoles, it is now possible for indie game developers to forge agreements with console manufacturers for broad distribution of their games.
Other indie game developers create game software for a number of video-game publishers on several gaming platforms. In recent years this model has been in decline; larger publishers, such as Electronic Arts and Activision, increasingly turn to internal studios (usually former independent developers acquired for their development needs).
Quality of life
Video game development is usually conducted in a casual business environment, with T-shirts and sandals common work attire. Many workers find this type of environment rewarding and pleasant professionally and personally. However, the industry also requires long working hours from its employees (sometimes to an extent seen as unsustainable). Employee burnout is not uncommon.
An entry-level programmer can make, on average, over $66,000 annually only if they are successful in obtaining a position in a medium to large video game company. An experienced game-development employee, depending on their expertise and experience, averaged roughly $73,000 in 2007. Indie game developers may only earn between $10,000 and $50,000 a year depending on how financially successful their titles are.
In addition to being part of the software industry, game development is also within the entertainment industry; most sectors of the entertainment industry (such as films and television) require long working hours and dedication from their employees, such as willingness to relocate and/or required to develop games that do not appeal to their personal taste. The creative rewards of work in the entertainment business attracts labor to the industry, creating a competitive labor market which demands a high level of commitment and performance from employees. Industry communities, such as the International Game Developers Association (IGDA), are conducting increasing discussions about the problem; they are concerned that working conditions in the industry cause significant deterioration in its employees' quality of life.
Some video game developers and publishers have been accused of the excessive invocation of "crunch time". "Crunch time" is the point at which the team is thought to be failing to achieve milestones needed to launch a game on schedule. The complexity of work flow, reliance on third-party deliverables, and the intangibles of artistic and aesthetic demands in video-game creation create difficulty in predicting milestones. The use of crunch time is also seen to be exploitative of the younger male-dominated workforce in video games, who have not had the time to establish a family and who were eager to advance within the industry by working long hours. Because crunch time tends to come from a combination of corporate practices as well as peer influence, the term "crunch culture" is often used to discuss video game development settings where crunch time may be seen as the norm rather than the exception.
Surveys from game developers in the 2000s showed the average working week was at least 46 hours for more than 60% of respondents; when crunch time occurs, workweeks of 60 to 80 hours, or in some cases, 100 hours or more, have been reported. Most game-development engineers and artists in the United States are considered salaried employees; as "exempt non-hourly-paid professionals", they are not subject to state laws governing overtime. An exception is California, where software developers are specifically protected by a minimum hourly wage to be considered exempt, which as of 2008 was set to $36 an hour.
When crunch time does occur, the publisher or developer may help encourage employees by offering "crunch meals" that are delivered to the offices. Once a product is delivered, and the necessity for crunch no longer required, some companies allow their employees to take paid time-off in compensation for the overtime hours they had put in, or may offer salary raises and bonuses for successful completion of the delivery milestone.
Crunch time has been used in the industry but until 2004 was generally not discussed openly. A 2004 survey by the International Game Developers Association (IGDA) found only about 3% of respondents did not work any overtime, and of those that did, nearly half were not compensated for overtime. Attention to crunch was brought to the forefront by Erin Hoffman, posting anonymously under the name "EA Spouse", in 2004, describing the working hours her husband had faced at Electronic Arts (EA). Besides creating discussion within the industry on the effects of a crunch culture, EA faced two class action lawsuits by EA employees, with both ultimately settled with EA paying back the employees by 2006. EA also announced it would reclassify some of its developers as hourly employees eligible for overtime but eliminating their stock options.
A similar situation occurred in January 2010, when a collective group of "Rockstar Spouses", the spouses of developers at Rockstar San Diego, posted an open letter criticizing the management of the studio for deteriorating working conditions for their significant others since March 2009, which included excessive crunch time. This was followed by several former Rockstar employees posting similar complaints of their time there. The IGDA considered that Rockstar's working conditions were exploitative and harmful.
Since these points, some companies in the industry have taken steps to eliminate crunch. In 2004, following Hoffman's blog, the IGDA issued a report on the negative consequences of crunch time on developers and their quality of life. A 2014 IGDA survey found nearly 20% of game developers did not see any crunch, and where there was crunch, the average number of hours worked had dropped from the prior 2004 survey: in 2004, 35% had said they worked between 65 and 80 hours per week, while by 2014, 35% said they had worked from 50 to 65 hours. A 2019 survey of developers by the Game Developers Conference found that nearly half still worked over 40-hour weeks on average with only 12% working more than 50 hours a week on average, though nearly 75% stated they had at least one period where they had worked more than 40 hours in a single week.
However, stories of crunch time still have brought more awareness that crunch remained an accepted practice in the game industry. Families of Rockstar developers for Red Dead Redemption 2 in October 2018 brought forth[colloquialism] similar concerns as the prior "Rockstar Spouse" case. Anonymous Epic Games employees speaking to Polygon spoke of crunch time with 70 to 100 hour weeks by some ever since they released Fortnite Battle Royale, which has drawn a playerbase of millions. While these employees were getting overtime pay, there remained issues of health concerns and inability to take time off without it being seen negatively on their performance.
Crunch time may or may not hamper a game's quality. Despite the crunch, both Red Dead Redemption games were critically praised; similarly, Retro Studios' Metroid Prime and Metroid Prime 2: Echoes, both which included periods of crunch time, are also recognized as high-quality games that were critically acclaimed upon release. On the other hand, Sonic Team's 2006 Sonic the Hedgehog game was rushed in development to meet deadlines for holiday sales that year, suffering in quality, and has become known as one of poorest-received video games. Crunch time at Starbreeze Studios and Overkill Software in developing Overkill's The Walking Dead, principally from multiple switches in game engine requiring nearly full restarts each time, led to a product that was critically panned for its quality and gameplay, and left both studios in financial distress.
Similar to other tech industries, video game developers are typically not unionized. This is a result of the industry being driven more by creativity and innovation rather than production, the lack of distinction between management and employees in the white-collar area, and that the pace at which the industry moves that makes union actions difficult to plan out. However, when situations related to crunch time become prevalent in the news, there have typically been followup discussions towards the potential to form a union. A survey performed by the International Game Developers Association in 2014 found that more than half of the 2,200 developers surveyed favored unionization.
In 2016, voice actors in the Screen Actors Guild‐American Federation of Television and Radio Artists (SAG-AFTRA) union doing work for video games struck several major publishers, demanding better royalty payments and provisions related to the safety of their vocal performances, when their union's standard contract was up for renewal. The voice actor strike lasted for over 300 days into 2017 before a new deal was made between SAG-AFTRA and the publishers. While this had some effects on a few games within the industry, it brought to the forefront the question of whether video game developers should unionize.
A grassroots movement, Game Workers Unite, was established around 2017 to discuss and debate issues related to unionization of game developers. The group came to the forefront during the March 2018 Game Developers Conference by holding a roundtable discussion with the International Game Developers Association (IGDA), the professional association for developers. Statements made by the IGDA's current executive director Jen MacLean relating to IGDA's activities had been seen by as anti-union, and Game Workers Unite desired to start a conversation to lay out the need for developers to unionize. In the wake of the sudden near-closure of Telltale Games in September 2018, the movement again called out for the industry to unionize. The movement argued that Telltale had not given any warning to its 250 employees let go, having hired additional staff as recently as a week prior, and left them without pensions or health-care options; it was further argued that the studio considered this a closure rather than layoffs, as to get around failure to notify required by the Worker Adjustment and Retraining Notification Act of 1988 preceding layoffs. The situation was argued to be "exploitive", as Telltale had been known to force its employees to frequently work under "crunch time" to deliver its games. By the end of 2018, a United Kingdom trade union, Game Workers Unite UK, an affiliate of the Game Workers Unite movement, had been legally established.
Following Activision Blizzard's financial report for the previous quarter in February 2019, the company said that they would be laying off around 775 employees (about 8% of their workforce) despite having record profits for that quarter. Further calls for unionization came from this news, including the AFL-CIO writing an open letter to video game developers encouraging them to unionize.
Game Workers Unite and the Communications Workers of America established a new campaign to push for unionization of video game developers, the Campaign to Organize Digital Employees (CODE), in January 2020. Initial efforts for CODE were aimed to determine what approach to unionization would be best suited for the video game industry. Whereas some video game employees believe they should follow the craft-based model used by SAG-AFTRA which would unionized based on job function, others feel an industry-wide union, regardless of job position, would be better.
Sweden presents a unique case where nearly all parts of its labor force, including white-collar jobs such as video game development, may engage with labor unions under the Employment Protection Act often through collective bargaining agreements. Developer DICE had reached its union agreements in 2004. Paradox Interactive became one of the first major publishers to support unionization efforts in June 2020 with its own agreements to cover its Swedish employees within two labor unions.
Some of the larger video game developers and publishers have also engaged contract workers through agencies to help add manpower in game development in part to alleviate crunch time from employees. Contractors are brought on for a fixed period and generally work similar hours as full-time staff members, assisting across all areas of video game development, but as contractors, do not get any benefits such as paid time-off or health care from the employer; they also are typically not credited on games that they work on for this reason. The practice itself is legal and common in other engineering and technology areas, and generally it is expected that this is meant to lead into a full-time position, or otherwise the end of the contract. But more recently, its use in the video game industry has been compared to Microsoft's past use of "permatemp", contract workers that were continually renewed and treated for all purposes as employees but received no benefits. While Microsoft has waned from the practice, the video game industry has adapted it more frequently. Around 10% of the workforce in video games is estimated to be from contract labor.
Demographics of game development
In 1989, according to Variety, women constituted only 3% of the gaming industry. By 2019, IGDA found 24% of its survey participants reported as female. According to Gamasutra's Game Developer Salary Survey 2014, women in the United States made 86 cents for every dollar men made. Game designing women had the closest equity, making 96 cents for every dollar men made in the same job, while audio professional women had the largest gap, making 68% of what men in the same position made.
Similarly, minority groups[when defined as?] are underrepresented in the video game industry. The 2019 IGDA Developer Survey found that 7% of its respondents identified as Hispanic/Latino, and 2% as black, in contrast to United States Census estimates in 2018 of 18% and 13% respectively. Asian groups tend to over-represented in the industry as well when compared to the United States data. In a 2014 & 2015 survey of job positions and salaries, the IGDA found that people of color were both underrepresented in senior management roles as well as underpaid in comparison to white developers. This racial diversity issue has similar ties to the gender one, and similar methods to result both have been suggested, such as improving grade school education, development of games that appeal beyond the white, male gamer stereotype, and identify toxic behavior in both video game workplaces and online communities that perputate discrimination against gender and race.
- Bethke, Erik k (2003). Game development and production. Texas: Wordware 2, Inc. p. 4. ISBN 1-55622-951-8.
- McGuire, Morgan; Jenkins, Odest Chadwicke (2009). Creating Games: Mechanics, Content, and Technology. Wellesley, Massachusetts: A K Peters. p. 25. ISBN 978-1-56881-305-9.
- Bob, Ogo. "Electronic Game School". Teacher. Archived from the original on 2018-10-12. Retrieved 2020-07-20.
- Bates, Bob (2004). Game Design (2nd ed.). Thomson Course Technology. p. 239. ISBN 1-59200-493-8.
- Gnade, Mike (July 15, 2010). "What Exactly is an Indie Game?". The Indie Game Magazine. Archived from the original on September 27, 2013. Retrieved January 9, 2011.
- Ahmed, Shahed. "Naughty Dog discusses being acquired by Sony". GameSpot.
- "Is Your Favorite Game Company Ripping You Off?". Next Generation. No. 30. Imagine Media. June 1997. pp. 39–40.
- "The Next Generation 1996 Lexicon A to Z: Second Party". Next Generation. No. 15. Imagine Media. March 1996. p. 40.
- Fahey, Mike (February 21, 2015). "The Studio Behind Smash Bros. And Kirby, HAL Laboratory Turns 35 Today". Kotaku. Retrieved March 25, 2021. CS1 maint: discouraged parameter (link)
- "Stream of video games is endless". Milwaukee Journal. 1982-12-26. pp. Business 1. Retrieved 10 January 2015.
- Flemming, Jeffrey. "The History Of Activision". Gamasutra. Archived from the original on December 20, 2016. Retrieved December 30, 2016.
- Mochizuki, Takahashi; Savov, Vlad (August 25, 2020). "Epic's Battle With Apple and Google Actually Dates Back to Pac-Man". Bloomberg News. Retrieved August 25, 2020.
- "The End Game: How Top Developers Sold Their Studios - Part One". www.gamasutra.com.
- McKay, Brett; McKay, Kate (September 29, 2010). "So You Want My Job: Video Game Producer". The Art of Manliness. Retrieved May 30, 2014.
- "EA: The Human Story". livejournal.com. 10 November 2004. Retrieved 6 November 2018.
- "Top Gaming Studios, Schools & Salaries". Big Fish Games. Archived from the original on 19 July 2013. Retrieved 30 July 2013.
- The Game Industry Salary Survey 2007 however, different regions and costs of living will add a wide range to the minimum and maximum pay scales. Most larger developers such as Ubisoft will include profit-sharing plans, royalty payments or performance-related bonuses to reward their employees. from GameCareerGuide.com
- Kris Graft (July 22, 2014). "Game Developer Salary Survey 2014: The results are in!". Gamasutra.
- Robinson, Evan (2005). "Why Crunch Mode Doesn't Work: Six Lessons". IGDA. Archived from the original on 2009-03-02. Retrieved 2009-03-07.
- Harkins, Peter Bhat (5 April 2009). "The Game Industry". Push.cox.
- Frauenheim, Ed (11 November 2004). "No fun for game developers?". CNet News.
- Dyer-Witheford, Nick; de Peuter, Greig (2006). "" EA Spouse" and the Crisis of Video Game Labour: Enjoyment, Exclusion, Exploitation, Exodus". Canadian Journal of Communication. 31 (3): 599-617. doi:10.22230/cjc.2006v31n3a1771.
- Paprocki, Matt (February 27, 2018). "EA Spouse, 14 Years Later: How One Person Tried Correcting EA Culture". Glixel. Archived from the original on February 27, 2018.
- McCarty, Jared (October 15, 2019). "Crunch Culture Consequences". Gamasutra. Retrieved February 3, 2020.
- Williams, Ian (February 18, 2015). "Crunched: has the games industry really stopped exploiting its workforce?". The Guardian. Retrieved January 20, 2020.
- Exemptions from Minimum Wage and Overtime from Texas Workforce Commission
- IWC. "California Code of Regulations, Title 8, Section 11170. Miscellaneous Employees". www.dir.ca.gov. Retrieved 6 November 2018.
- Cogdill. "SB 929 Senate Bill - CHAPTERED". www.leginfo.ca.gov. Retrieved 6 November 2018.
- McShaffry 2009, p. 17.
- Moore & Novak 2010, p. 212.
- 'EA Spouse' Weblog Raises Issues On Game Development Quality Of Life from Gamasutra
- Bramwell, Tom (January 11, 2010). ""Rockstar Spouse" attacks dev conditions". Eurogamer. Retrieved October 31, 2017.
- Brice, Kath (January 11, 2010). ""Rockstar Spouse" accuses dev of pushing its employees "to the brink"". GamesIndustry.biz. Retrieved October 31, 2017.
- McWhertor, Michael (January 14, 2010). "IGDA Condemns Alleged Rockstar Work Conditions As "Exploitative, Harmful"". Kotaku. Retrieved October 31, 2017.
- "Quality of Life White Paper". International Game Developers Association. Archived from the original on May 19, 2008. Retrieved October 23, 2004.
- "GDC State of the Industry: Nearly half of game makers still work over 40 hours/week". Gamasutra. February 3, 2020. Retrieved February 3, 2020.
- Schreier, Jason (October 23, 2018). "Inside Rockstar Games' Culture Of Crunch". Kotaku. Retrieved October 23, 2018.
- Campbell, Colin (April 23, 2019). "How Fortnite's success led to months of intense crunch at Epic Games". Polygon. Retrieved April 23, 2019.
- Casamassina, Matt (August 28, 2009). "A Space Bounty Hunter in Texas". IGN. Archived from the original on September 28, 2012. Retrieved April 28, 2010.
- Walker, Bryan; Kelbaugh, Michael (December 3, 2004). "Post game report: Retro Studios talk Metroid Prime 2 Echoes". Computer and Video Games (Interview). Interviewed by NOM staff. Archived from the original on March 9, 2012. Retrieved November 30, 2008.
- 社長が訊く『メトロイドプライム3 コラプション』 [Iwata Asks: Metroid Prime 3: Corruption]. Nintendo (in Japanese). Archived from the original on January 5, 2012. Retrieved January 31, 2012.
- "Metroid Prime reviews". Metacritic. Archived from the original on November 21, 2010. Retrieved September 8, 2006.
- "Metroid Prime 2: Echoes Reviews". Game Rankings. Archived from the original on March 9, 2009. Retrieved October 18, 2008.
- Fahey, Mike (November 15, 2016). "Ten Years Ago Sonic The Hedgehog Was At Its Worst". Kotaku Australia. Gawker Media. Archived from the original on November 17, 2016. Retrieved March 18, 2017.
- Yin-Poole, Wesley (January 28, 2019). "The fall of Starbreeze". Eurogamer. Retrieved January 28, 2019.
- Maiberg, Emanuel (February 22, 2017). "Walk the Line". Vice. Archived from the original on February 22, 2017. Retrieved February 23, 2017.
- Sinclair, Brendan (June 24, 2014). "56% of devs in favor of unionizing - IGDA". GamesIndustry.biz. Retrieved March 22, 2018.
- Crecente, Brian (March 21, 2018). "Union Reps Meet With Game Devs About Unionization". Glixel. Retrieved March 22, 2018.
- Williams, Ian (March 23, 2018). "After Destroying Lives For Decades, Gaming Is Finally Talking Unionization". Vice. Retrieved March 23, 2018.
- Frank, Allegra (March 21, 2018). "This is the group using GDC to bolster game studio unionization efforts". Polygon. Retrieved September 24, 2018.
- Gach, Ethan (September 24, 2018). "Telltale Employees Left Stunned By Company Closure, No Severance". Kotaku. Retrieved September 24, 2018.
- Handradan, Matthew (September 24, 2018). "Telltale's treatment of staff "a problem endemic in the industry"". GamesIndustry.biz. Retrieved September 24, 2018.
- Fogel, Stephanie (December 14, 2018). "Game Workers Unite UK Is That Country's First Games Industry Union". Variety. Retrieved January 29, 2019.
- Takahashi, Dean (January 24, 2019). "GDC survey: Half of game developers support unionization, believe Steam is too greedy". Venture Beat. Retrieved January 24, 2019.
- McAloon, Alissa (February 15, 2019). "US labor organization AFL-CIO urges game developers to unionize in open letter". Gamasutra. Retrieved February 15, 2019.
- Dean, Sam (January 7, 2020). "Major union launches campaign to organize video game and tech workers". The Los Angeles Times. Retrieved January 7, 2020.
- Fridén, Eric (October 23, 2013). "Scandinavian Crunch: Pid Developer Might and Delight Goes Its Own Way". Polygon. Retrieved June 3, 2020.
- Olsen, Mathew (June 3, 2020). "Paradox Reaches Agreement With Swedish Unions For Better Pay, Benefits, And More". USGamer. Retrieved June 3, 2020.
- Schreier, Jason (August 27, 2020). "Blockbuster Video Games Mint Millions While Grunts Get Exploited". Bloomberg News. Retrieved August 27, 2020.
- Campbell, Colin (December 19, 2016). "The game industry's disposable workers". Polygon. Retrieved August 27, 2020.
- Marc Graser (October 1, 2013). "Videogame Biz: Women Still Very Much in the Minority". Variety. Retrieved 2013-10-20.
- "Developer Satisfaction Survey 2019 Summary Report" (PDF). International Game Developers Association. November 20, 2019. Retrieved June 4, 2020.
- Graft, Kris (July 22, 2014). "Gender wage gap: How the game industry compares to the U.S. average". Gamasutra. Retrieved December 27, 2015.
- "Developer Satisfaction Survey 2014 & 2015 - Diversity in the Games Industry Report" (PDF). International Game Developers Association. 2016-09-12. Retrieved June 4, 2020.
- Ramanan, Chella (March 15, 2017). "The video game industry has a diversity problem – but it can be fixed". The Guardian. Retrieved March 15, 2017.
- McShaffry, Mike (2009). Game Coding Complete. Hingham, Massachusetts: Charles River Media. ISBN 978-1-58450-680-5.
- Moore, Michael E.; Novak, Jeannie (2010). Game Industry Career Guide. Delmar: Cengage Learning. ISBN 978-1-4283-7647-2.