What 90s Game Dev Teaches Us About AI and the Future of Software Engineering
While the speed of disruption from AI feels unprecedented, we can look to history to see what happens when a technical industry undergoes a massive, orders-of-magnitude jump in developer productivity. If you want to see this playbook in action, look at the video game industry. The Era of Floppy Disks and Bespoke Engines In the early 1990s, when a studio built a new game, there were no ubiquitous…
The video game industry in the early 1990s was characterized by bespoke, ground-up rendering codebases for each major title. Collaboration was limited, with integration requiring physical transfer of files via floppy disks. Game development teams were small, with projects like Final Fantasy and Wolfenstein 3D requiring a core team of around 7 and 6 people respectively.
As productivity tools emerged, commercial engines and version control systems like Git made development faster and more efficient. By the time of Quake, a team of around 9 core developers could create true 3D gaming experiences in two years of intense work. Since then, game development productivity has increased dramatically, allowing a single developer to create a functional 3D prototype in 48 hours.
This has led to an expansion of the workforce, with end-game credits often running for 30-40 minutes and studios employing specialized teams for procedural physics. The Jevons Paradox suggests that as software production becomes cheaper and faster, the total number of developers and the complexity of software systems will increase, not decrease.
This same trend is expected to play out with AI and general software engineering, creating increasingly complex and immersive systems that will require specialized roles that today seem unimaginable.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
