Game development has become an increasingly popular career path in recent years, and there is a growing debate about whether game developers should play the games they create.
While some argue that playing a game may make it too familiar for developers to evaluate its mechanics objectively, others believe that playing a game can be emotionally taxing to see a project one has poured so much time and effort into. In this expanded article, we will delve deeper into the topic and explore both sides of the argument while providing some real-life examples to help you make your own decision.
Pros of Playing Games as a Developer
One of the main benefits of playing games as a developer is that it allows you to stay connected with your target audience. By playing your own game, you can gain valuable insights into what players enjoy and don’t enjoy about it. This information can then be used to make improvements and enhance the overall gaming experience for all players.
Additionally, playing games as a developer can also be a great way to relax and unwind after a long day of work. It provides a much-needed break from the pressures of creating games and can give you a fresh perspective on your own projects. This is particularly important in an industry that can often be very stressful and demanding.
Cons of Playing Games as a Developer
While there are certainly benefits to playing games as a developer, there are also some potential challenges that you should be aware of. One of the main concerns is familiarity with mechanics. If you play a game too much, it can become too familiar and affect your ability to objectively evaluate its mechanics. This can be particularly problematic when you’re trying to design new and innovative gameplay experiences for players.
Another potential challenge of playing games as a developer is emotional taxation. Creating a game from scratch requires immense dedication, creativity, and effort. If you’ve poured your heart and soul into a project, it can be difficult to see it objectively and critically. This can lead to burnout and make it harder to improve upon your work.
Real-Life Examples
Despite the potential challenges of playing games as a developer, there are many successful game developers who do enjoy playing their own games. One such example is Shigeru Miyamoto, the creator of Super Mario Bros. and The Legend of Zelda. While he’s undoubtedly a busy man running Nintendo, he still makes time to play his own games and has even been known to share his feedback with the development team.
Another example is Markus Persson, the creator of Minecraft. Despite the success of his game, Persson has been very open about his dislike for certain aspects of it, such as the multiplayer mode. However, he’s also been quick to address player feedback and make changes to improve the game based on their suggestions.
Ultimately, whether or not you choose to play your own games is a personal decision that depends on your individual circumstances and priorities. If you find that playing your own game interferes with your ability to objectively evaluate its mechanics or causes emotional taxation, it may be best to step back and focus on other aspects of the development process. However, if you enjoy playing games and find that it helps you stay connected with your target audience and provides a much-needed break from the pressures of creating games, then there’s no reason why you can’t continue to play them as part of your job.
In conclusion, whether or not game developers should play their own games is a complex issue that requires careful consideration of both the pros and cons. While playing games as a developer can provide valuable insights into what players enjoy and help you relax after a long day of work