• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
  • entries
    625
  • comments
    1446
  • views
    1006498

Time Management and Multiple Personalities

Sign in to follow this  
Followers 0
ApochPiQ

320 views

Originally, I set out to do a sort of "Day in My Life" entry, that broke down what I do at my job on a per-hour basis. I started 2 days ago around 6:30 AM, which is when I woke up. [My sleep schedule has been totally random lately, which is partly really cool, and partly really disorienting.] I then logged what I was doing for the next massive chunk of time (close to 28 hours, not including an incidental nap).

Unfortunately, it didn't work out so well as a journal entry. Often I'd just totally forget to log what happened for a few hours, leaving weird gaps and mysterious inconsistencies in my accounting of time. Once I just fell asleep for 6 hours. Worse, most of the notes I kept were really trifling little blobs; they aren't interesting to anyone who isn't working on the project. After a while, I started just interjecting stupid thoughts and observations, and it became a mass of jumbled idiocy that was neither fun nor informative to read.

So I chucked it out. There really wasn't much use to it, and it wasn't worth the time.


That's not what I find interesting, though. One curious side-effect was how it affected my work patterns. I started to see little web-surfing breaks as massive chunks of time, rather than just vague "oh, look, it's getting dark out and I still haven't done any work." Quantifying the amount of time I spent working and goofing off really made me feel like an idiot for slacking around too much, so I ended up doing a lot more work instead.

That much wasn't too surprising - time logging is a well-known technique for time management. What was really different was the way my thought process was affected. In taking notes on what I was doing, I had to justify aloud some of my design decisions. Now these decisions are all made with discussion and agreement from the rest of the team, so they're by no means arbitrary and off-the-cuff things. Yet, when I started trying to explain them in a way that would make sense to an outsider, I started seeing all kinds of new opportunities to make even better decisions.

Discussing and verbalizing design decisions is not a surprising new technique, either; I've been doing it for years. It's part of why team programming (and micro-scale practices like pair programming) is such an effective tool when used correctly. It's a sort of extra mind to make sure that everything is sane and sensible.

So often, though, that extra mind is an insider, and if one insider is prone to make some oversight or bad decision, another insider is just as vulnerable. We all get so involved in the system that we can't see beyond it, and at some points, even peer-review won't catch the really deep, subtle, and subconscious assumptions that give designs the most trouble.

When I get into a system, learn it, and start to develop a zone-sense for it, I get a sort of holistic, top-down feel for how it all works. I have an intuitive feel for what will happen if I poke the system in certain ways, and that by and large is how I do design. For the most part, this works great; but the danger is that one can get too accustomed to that sense. One might know how the system works now, but when doing refactoring and redesign, that is not enough information. You have to know what else could be. A redesign requires you to step outside the system, look at all of the truly available options, and consider them objectively. Getting stuck in a rut of "how it already works" can be deadly.


So, the next time you go to adjust a design, develop multiple personalities. Create an imaginary friend that has never touched your system before, knows nothing about the design, and maybe even isn't a programmer/designer. Then justify everything you do to this imaginary friend. Avoid the temptation to make excuses and empty rationalizations; really sell this guy on what you're doing, and why it's the best possible choice.

0
Sign in to follow this  
Followers 0


1 Comment


My imaginary friend totally agrees with you. I on the other hand believe you and him are just trying to rob me of web time. [grin]
0

Share this comment


Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now