[The following are just bits and pieces from a different times and places that together aim to create a mosaic experience of a regular day in a certain gamedev role. Does not represent any real events!]
08:39 - I arrive to my workplace. Iâm booting my laptop, making coffee, saying âhiâ to some early comers. The office seems very calm at that time. No wonder why programmers like to work in the mornings. Sometimes itâs the only period of the day when you have a fresh mind and a quiet surroundings at one moment.
08:54 â Mails, mails, mails. Got one from Apple saying that they like our game and asking us for some banners at a designated sizes. Being featured always boosts teamsâ morale. Since we have worked with a mobile publisher recently weâve prepared those assets beforehand. Thatâs a quick one. Next. Some bugs are pouring in concerning our latest console version. Not fun. Iâll file it into our system but probably wonât do much more with it now. Making a console game update isnât all that easy so we would have to have a really good reason to take up this task. On the upside, their certification process is very thorough so the chances of a major bug are relatively slim. Next. Some VO actor from Hawaii send us some sample recordings. ManâŚ he clearly did not understand the note saying: âtry NOT to sound funnyâ. I have to thank him for the effort though. Next.
09: 33 â Short stand-up meeting interrupts my correspondence review. There are only two weeks left for the prototype of our new game to be finished. Core team (3 people) is very excited to show to the rest what they were working on but at the same time a bit worried because of some negative feedback theyâve received last Friday from few people who played first two levels. The meeting was about clarifying the rules of the game in order to make it more understandable. Itâs good that they did not ignore the problem at such an early stage. I wonder if they will be able to do something about it though.
09:50 â Got an invitation for a conference. This time itâs in Wroclaw but it seems pretty small. Nevertheless, my friends really wanted me to come and give a lecture. Plus, I have one of those New Yearâs resolutions (and all others have already been forgotten) to keep sharpening my presentation skills. I guess Iâll go. Itâll be fun.Â
10:05 â I like to read some positive comments posted under our game by satisfied customers. Things like âMy daughter really likes your game, so I like it too because sheâs quiet for hours while playingâ make me think that our work translates into somebodyâs better day. I tend to print out some of those texts and stick it on the studioâs kitchen door for the team to see. Iâm not sure if itâs making my colleagues feel better but I guess it wonât hurt.
10:21 â Plan updates. I have to make sure that everybody knows what they need to be doing and how much time left they have but try not to be too insistent/annoying. Sometimes it gets really tough. For example, a programmer doesnât have a lot specifics of a certain feature while a designer hadnât had a chance to get round to think about them. Ultimately, what they can give me is a rough estimate based on a vague assumption. In my world itâs like a house of cards build on a swamp but I guess I wonât get any more out of them today.
12:34 â Lunch ordering time. Every time I gather orders from a few dozen people I keep remembering some interviews with a well-known game devs who were saying that while they work on their authority and position in the workplace, they also do not run away from such a trivial supporting tasks like ordering food for their teams. I can relate to that :)
13:42 â A meeting is being hosted. Itâs about our nearest deadline. It turns out that our publisher did not like the fact that we command the same set of troops throughout the whole game. In their opinion there should be some evident progress visible for the player. We argued that itâs a mini-strategy game, not RPG, so the character evolution isnât that crucial. But no. We had to do something about it. All in all, we agreed that we will be tinting the colors of troopsâ clothes level after level. It seems a bit dumb for me personally but thatâs not my decision to make.
15:03 â Localization team dropped me an e-mail with the fully localized app description. Â I was anxiously waiting for that because we were about to publish the build on the store. Now that I have it I wonât do it just yet. Thatâs a desert of my job so letâs save it for later.
15:14 â Planning. Some changes have to be made. We all agreed that we need to throw more assets at UI implementation because this has become an unexpected critical path in the main project. That requires a bit of reshuffling from me. Switching to the next project. Here I failed to convince my team about the need of reassigning some key artists from making trees to creating the first two vehicles for the game. Their argument was that a forest plays a big part in the game so it needs a top-notch trees. Even if that means spending more than a month on researching the right tree qualityâŚ
16:34 â Got an e-mail from our sound engineer. He made a couple of new UI sounds but did not answer my question about environmental sounds. That may mean that he either dislikes the idea or just did not have time to sit on the topic. Thatâs predictable because outsourcers do not have a rigid working schedule. Until all the deadlines are met we are fine with a little elasticity here, but I have to remind him about that because we donât want this task to slip too far, do we?
16:50 â More plan updates. When Iâm thinking of being done at a certain hour I smile a little because it rather looks like 10 minutes of mail, then a talk, then a short phone call, then a talk with another person, then a remark for the whole team, another mail etc. But letâs say that around this hour I consider yet another round of updates for everybody omitted in the morning, those who should finish their tasks or those who are directly affected by the recent changes in the plan and should know about it.
18:15 â The day is coming to an end. Red sticky card keeps reminding me that I need to publish a game today. Setting up a release in Google Play is sooooo easy. I wish that consoles have this level of process simplicity. Pasting the description in a dozen languages is like dressing the cake that you are about to eat. Everything is done and tested. The whole process is over. Click âsaveâ, then âpublishâ and itâs done.
18:35 â Late talks over minor tasks. Most of the people leave their low-priority things for this hour. Also many already went out so itâs quiet again. It is easy to hear any conversation in our open space area with only few people left out. That and all the âactionâ of the day triggers many talks. Almost philosophical chats about taking up a lead role, responsibility, estimation, future projectsâŚ I really enjoy that. It takes a lot of pressure off the team and substitutes it with sincerity that is sometimes absent in group discussions.
18:45 â Ok. I guess Iâm done for today. Time to head back home.
19:59 â Sandwiches for supper. Itâs surprising that one can get so much self-efficacy simply by preparing a meal. I mean, cooking in general is one of those things in which your work transfers into a very tangible result in a matter of minutes. If you consider that gamedev is working on visions, ideas and small functionalities that come together after 8-24 months getting an instant final result with a sandwich certainly is something different. :)
20:31 â Checking work mail from home. I know, Iâm workaholic but consider that Iâm operating in Poland which is 7-9 hours ahead from different parts of the USA. That implies a delay in any mailing contact which sometimes can be very annoying. For instance, if you are learning (like me) how to publish a game on a console you need to contact hardware manufacturers and ask about a ton of stuff. Five such âlateâ e-mails in a week and Iâm speeding up the conversation by 100%.
21:33 â Reading a book. Itâs really hard to concentrate. I keep revisiting all the major arguments at work. Thinking about alternative perspectives and how to address certain people differently another time. It takes only a few lines of mere work-related text to bring up in my mind one of many pipelines set up in the project. Oh sh**, when we discussed additional tutorials we forgot to include some text proofreading costs. I have to remember that tomorrow.
23:09 â Watching a movie. In the meantime I write some notes on my phone that I should approach one of the programmers tomorrow during a coffee break and try to express my appreciation of his work. I realized that he was constantly being bombarded by me with tasks and all he hears it âdo this or thatâ... that kinda sucks. A few weeks in such conditions and heâll hate me to the bone. No good comes from that.
00:31 â I go to sleep thinking: âThat wasnât such a bad day, but I can do better tomorrow.â
I wouldnât trade this job for anything. Iâm a producer. :)