Monday, November 11, 2013

Diretide Where?

The gaming world saw and interesting occurrence just a few weeks ago. Fans of developer Valve's action-rpg Dota 2 were teeming on messaging boards and social media asking one sole question. Diretide Where?

Diretide is a Halloween themed event within Dota, where additional gamemodes and new mechanics bring about a festive way to celebrate the holiday, and Dota fans love it, but that love turned to vitriol upon the arrival of October 31st, when there was no Diretide update to the Dota client. Fans were seen to be spamming forums, emails to valve, even tagging the car company Volvo in twitter posts expressing concern.


It took them nearly two weeks, but Valve finally responded with this letter.


Not My Best Work!

"Whenever we make a significant mistake, we spend a bunch of time looking at what happened, why it happened, and how we can fix it. Most of the time we do this privately, but in our recent mistake around Diretide, we felt sharing our analysis with you made sense.
First, what happened – we didn’t ship a Diretide event this year, and you were rightly upset about it. That was clearly a mistake, and then we compounded the problem by not telling you what was going on.
So, why didn’t we ship Diretide?
  • We have a huge update in the works that looked like it would be finished in time for Halloween. Stopping that update to work on Diretide seemed like something you would actually be unhappy with us for, because the update is pretty significant. More on that later.
  • Turning on last year’s Diretide event wasn’t trivial. We’d done a year of work on the game which had changed our codebase, UI, and other systems enough that we would need to do some work to resurrect it.
  • We underestimated how much you wanted Diretide.
  • We made the decision a while ago, and failed to employ our usual process of regularly asking ourselves whether we were still on the right track. There were a bunch of people on the Dota 2 team who poked at the decision to not do it as Halloween approached, but due to how busy everyone was with our next major update, no-one really took the time to step back and objectively realise we were being collectively crazy.
Due to our poor prediction of your reaction, and the team being focused on the next update, we didn’t spend enough time thinking about talking to you about our decision. As a result, by the time we’d realized we’d made a bad decision, the pitchforks were out.
Then, why didn’t we communicate with you what was going on?
  • You were already mad and disappointed in the lack of Diretide. Telling you that you weren’t getting it at all wouldn’t have really helped much. Now we started thinking in terms not of “what should we say?”, but in terms of “what should we do?”
  • We were, and still are, confident that you’ll be happy when you see what’s in the next update (which isn’t far away now).
Now, what is the fix?
First, we’re going to ship Diretide with the next update. The rest of the update we’ve been working on is in final testing, and as each of us finish up our work on it, we’ve been jumping over to Diretide. Second, we’re pretty sure the update that we’ve been working on for a couple of months is going to be pretty significant. In addition, we’ve made a few changes to Diretide that we think makes it more fun than before. And while we always want the community to tell us exactly how we’re doing, this is probably a good time to stop cc’ing innocent car manufacturers with your messages.
Paying attention to what is happening in the community around Dota 2 is one of the most important aspects of what we do at Valve. And while we are clearly not mistake-proof, hopefully it is useful for us to walk everyone through our process for recognizing and then fixing our mistakes."

Valve, while recognizing its mistake, manages to salvage its sterling reputation with its community by not only delivering an explanation, but by putting in the effort to reconcile this problem that they had created. Delivering Diretide late is certainly not what fans had hoped for, but it is better to have Diretide tardy than to never have had Diretide at all.

Tuesday, October 29, 2013

Responsible Software Development

   
     I'm certain that a fair amount of people would consider the nuts and bolts of software design to be the basis for ethical discussion in the field, but I'd like to posit the idea that the majority of the responsibility for the development of an ethically appropriate product falls to the developers instead of the designers.

      Designers come up with frameworks, workflow, ideas, things that in their infancy are completely intangible, and the way those ideas in their gestation become functioning products sometimes leaves the mind less grandeur, and more disappointment. The designers mean well, but in an environment where the people with the plans are not the same people doing the building, inevitably the plan will have to change; and in a well conditioned work environment, that system of change should be easy. The developers on the ground level of the project should be able to speak about the functionality, feasibility, and efficacy of the product at any point in its construction. In this way, deadlines can be kept, profit margins can be maintained, and, most importantly, the product that is being developed will be as ethically sound in its engineering as it is in its design. Preservation of this type of communication is key to being able to responsibly function in a software-based workspace, as without it the flaws that are discovered to be inherent to the nature of the project cannot be discussed, and as such, a product will be produced that does not work as it was intended to work, and that is irresponsible.

     Outside of the communication about the design process, developers also must maintain their integrity in their individual work. The final outcome of the project rests on the trust that the team has in their ability to complete the task to the best of their ability, and to be honest about its flaws. The individual developer must be willing to work through the most difficult problems in a project, and not take shortcuts that would hurt the product but increase his efficiency. He must keep the goal of having as near to a perfect product in his mind at all times. With that mindset, he can go about his work ensuring that the bugs and issues that he finds will be rectified, and that at the end of the project, he has completed his work to the absolute best of his ability.

     With these two key points in mind, we can imagine the perfect marriage of design and development. An environment in which communication is open, individuals maintain their integrity and moral compass, and everyone involved in the project is working their hardest to see the task fulfilled exceptionally. It is a hard standard to try to hold to, but if it could be achieved, the quality of the products coming out of that team would be only limited to the capabilities of the people working in it, and there would be no need for concern about whether or not the product meets ethical standards.