• 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.
Sign in to follow this  
Followers 0
tom_mai78101

How many projects do you need realistically so that you're starting to get attention?

4 posts in this topic

Currently, I am working on an Android project single-handedly. While working on it, a thought popped into my mind. How many projects should I have to make, in a realistic way, so that I may be able to get someone to be impressed with my work?

If I were to write a resume and wanted to add my project onto it, even if it's just one, what should I say about it? Should it be something that's obvious to anyone, something anyone can describe it once they played around with my project, or something that tells others what needs to be improved, what could make it work even more, or what will this project behold upon me?

Thanks in advance, looking forward to reading any feedback. Edited by tom_mai78101
0

Share this post


Link to post
Share on other sites
Having a single impressive project is much better than having a thousand mediocre projects.

No one is going to be impressed with your work if your work is not impressive, no matter how much work you do. It's better to focus on making each project as good as you can within reason, and make sure you finish your projects.

As for putting work experience and past projects on your resume, you should describe what role/position you held (if applicable), and a brief summary of what you worked on (or at least the most important items). Being concise is best. If you coded and built all the assets for a project, don't list each thing you worked on, simply mention that you were the only developer on the project.
2

Share this post


Link to post
Share on other sites
Understood. Other than just mentioning that I'm the only developer on my project, anything else I should write down about the whole project? How concise should I be in describing the project?

Like, using my project's assets as an instance for example, I drew some of the designs based on simple geometric shapes, and rely on simple game mechanics to maintain a steady game play experience. Based on the excerpt, I feel it's concise enough to give a picture, but it's unable to convince myself that this is how I should describe it, even though it's the actual truth.

I could not manage myself to over-emphasize my work when all the work that was done is easy to describe without giving much thought.
0

Share this post


Link to post
Share on other sites
List a few relevant (to the job being applied for) things you are proud to have worked on (single-handedly developed game X could be a bullet point for instance). Being easy to describe usually means easy to understand, which is good for a resume.

Don't "over-emphasize" your work, just describe what you worked on. i.e.:

Game X (Android)
-Built game X using UnrealEngine 3 (shows experience with unreal)
-Built soft-body physics system to support blob enemies. (shows experience with physics/math)
-Built Scalable AI architecture that makes use of parallel processing to support large number of characters (shows experience with AI, and systems running across multiple cores)


It doesn't need to get more detailed than that on resumes. That's what interviews are for.

Just remember that entry-level positions don't require experience, and without work experience your resume won't be very long (1 page, 2 MAX if you have a TON of good and relevant personal projects).
0

Share this post


Link to post
Share on other sites

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
Sign in to follow this  
Followers 0