Urgent.News

What's breaking now, across thousands of outlets.

Tech

The five golden rules of external development

We created Code Wizards 24 years ago, and as an external development partner, we work with a mix of small and large companies on backend engineering, live operations, IT and more. Over the years we've learnt from our mistakes, and CEOs of new studios and service providers often ask me how they can best work together for success. Here, I'll share the top five simple rules that you can incorporate…

The five golden rules of external development

In 1998, Code Wizards was established as an external development partner for both small and large companies, working on various aspects of game development such as backend engineering, live operations, and more. Over the years, the company has learned valuable lessons from its experiences and has compiled a list of five golden rules for successful external development partnerships. These rules aim to minimize stress and maximize enjoyment in the collaborative process.

Firstly, trust is crucial from the very beginning of any engagement. Building trust takes time, but with a new partner, it is essential to establish trust from day one. This can be achieved by consistently demonstrating trustworthiness through transparency, planning, and progress monitoring. Both parties must trust each other, as feedback from the client is often valuable and should be taken seriously.

Secondly, it is vital to communicate any issues or concerns immediately. Games are intricate works of art, and even small details can significantly impact the overall experience. If something feels off, sharing that feedback promptly is crucial, as it helps ensure the final product is fun, beautiful, and engaging. This communication should be open and honest, with all parties feeling valued and their input considered.

Thirdly, a strong collaboration is built on trust and mutual understanding. As the game evolves, all team members need to be willing to adapt to changes and work together to make the necessary adjustments. This includes understanding different communication styles and cultural nuances, as well as being open to constructive criticism and feedback. By fostering an environment where everyone feels comfortable sharing their thoughts and concerns, the team can more effectively address any issues that arise.

Fourthly, overcommunication is key to maintaining a smooth development process. Initial stages of a game production cycle may involve more artistic and free-flowing communication, but as the project progresses, focus should shift towards addressing any risks, changes, or dependencies that could affect the project. Tailoring communication styles to suit the needs of each team member and the specific stage of the game development is essential.

Lastly, reputation matters greatly in the gaming industry, as it is relatively small and interconnected. Building a positive reputation requires consistent trustworthiness, even during challenging times. When mistakes are made, it is essential to own up to them and work together to rectify the situation. At the same time, it is also important to recognize and support others when they encounter difficulties.

By maintaining a strong reputation, both parties can continue to trust and collaborate effectively, ultimately resulting in a better game.

Written by urgent.news from GamesIndustry's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at gamesindustry.biz →

More in Tech

BOLA, the #1 API Vulnerability: a One-Line Fix and an A-B Test in Go and PHP

An invoicing application exposes an API : web addresses, or URLs, that other programs call to read or change invoices. Bob is logged in with his account.

  • BOLA (Broken Object Level Authorization) ranks as top API vulnerability in 2023
  • Fix involves single line of code checking user ownership of invoice
  • Test requires two accounts: one to create invoice, another to access it expecting 404

Activate WP_DEBUG and read debug.log without breaking the site in production

A site that crashes without saying anything is a site that is hiding the answer from you. WordPress knows about it, it simply refuses to display it, and this is intentional: showing a PHP trace to…

  • Activate WPDEBUG and set WPDEBUGLOG to true in wp-config.php
  • Disable WPDEBUGDISPLAY to prevent errors from showing to visitors
  • Check debug.log for Fatal, Warning, and Notice messages to diagnose issues

More from Thursday 29 October →