Short schedules, GDC talks and arbitrary design
My previous dev blogs have been mostly about the WHAT of my development process, WHAT I did, WHAT I learned and sometimes HOW I came about it. And while that is all well and good it isn’t what is truly bringing Twin Switch to life. This dev log has taken some time to write because I have had trouble articulating my thoughts into a format that would be academically acceptable. But this dev blog should’t be for my school (even though it is being marked), it should be for me and whoever happens to read it. A question I have recently been asking myself is “What would I want to read a dev blog about?” Sure it would be interesting to read about some new technique or how a pipeline either succeeded or failed. But those are all results of a persons work, they’re results of their WHY. And that’s what this dev blog is about.
This dev blog is about WHY I choose to work on Twin Switch and WHY it’s important to know WHY you’re doing what you do.
If you were to ask the average student WHAT they want to do after graduation you will always get the same response, even from me most of the time. “I want a job”. If you were to ask them HOW they were going to do that they would probably say something along the lines of “By working hard or making a good game”, you would get a generic response that is more vague than asking them WHAT. But if you were to ask the average student WHY they wanted the job, I can guarantee you 90% would not be able to answer that question. Many of them would say they so they could make money or become successful but those are simply results. The average student would answer WHY with more WHATS.
By asking WHY are you making games I mean WHY do you come to school, WHY do you put in this effort? Not to get good grades or get a good job, but intrinsically, WHY do you want to make games.
Being able to answer this WHY is arguably much more important than any dev blog about skills and techniques because those can be achieved by anyone. There are thousands out there that all go over the same stuff, resources will always be available to you to improve you practical skill. But asking WHY goes beyond that, its not something a dev blog or tutorial video can answer for you. It’s a concept that has to be introduced and learned through working.
So WHY do I work so hard on Twin Switch? WHY do I put the game before my school work? WHY do I break the normal format of a dev blog opening the possibility of receiving a bad grade? Because I believe Twin Switch is more important than all of that. This whole program has been about teaching students WHAT to make and HOW to make it, but it cannot teach the students WHY they should make them, that has to be discovered individually and sadly, rarely is.
You see a good programmer, a good designer and a good artist don’t make a game good, you can have the best people in the world working on your game but if they are not working for a purpose you just don’t get anything very good. Everyone in the world has access to the exact same resources, every game company is just a qualified as the next to make good games but the ones that produce good work are the ones that believe in what they do. The companies that succeed have a WHY. They know WHY they get out of bed in the morning. They don’t go to work for a paycheck, they work because they believe what they do is more important than they are. They belong to something bigger and more beautiful than any one individual.
Needs to be continued…