• 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

Are these projects some things I cannot abandon, no matter how incomplete it is?

1 post in this topic

I have put some projects up on another forum, just so a few acquaintances of mine can try them out. Below are the given links to each project. For those who are interested, please test them out, and if possible, do provide feedback in this thread. Thank you!


Pokémon Walking Algorithm (Working title, not complete) [Game, Java]

5-way Bluetooth Relay App (Requires 5 devices for testing, which I don't have) [App, Android]

Marble Run (Complete, albeit a few minor bugs) [Game, Android]

Rest Timer (Complete) [App, Android]


I was wondering if these are eligible for my portfolio, as in, since these projects (Marble Run is a large project, for me) are done in my college years, do they mean anything else I haven't seen yet, other than that they are currently abandoned in my portfolio? Should I not forgo "tossing into the bin" mindset for these projects?


I do not have a general threshold for what goes into my portfolio, nor do I understand what a portfolio should do besides keeping projects in one place. :(


Please tell me any suggestions to what I should do to transition around this, if possible. Sort of like, a minor change to something A, or a big helpful tip about something B. Thanks for your feedback, even if you're not replying. Everything you say or don't say is appreciated, regardless if I'm getting blamed on or something. <3


Share this post

Link to post
Share on other sites

Well I don't have an Android so I can't test most of your projects (I don't have much time right now anyway) but these are some generic opinions about portfolios:


I do not have a general threshold for what goes into my portfolio, nor do I understand what a portfolio should do besides keeping projects in one place


A portfolio isn't a code repository to store all your stuff. It's a hall of fame of your masterpieces to show to potential employers, used to optimize your chances of being hired, as well as generally documenting your skills in the best possible light. You should probably only put your very best projects there, and they need to be reasonably complete, e.g. they don't need to be utterly flawless but you want them to at least be functioning on some level and demonstrating something that you wish to emphasize such as gameplay elements, good performance, elegant art, interesting music, etc..


Don't put too much in your portfolio, especially very similar projects. They are not supposed to be code bases (though they can act as such, e.g. a github account you can use for effectively programming while still acting as a decent portfolio by making a good README.md file containing an overview of such and such project).


Never put trivial stuff in your portfolio, e.g. a two-line code snippet, unless it is ridiculously clever and earth-shattering. Similarly, don't put things you are not proud of in it (for this, there's always the Coding Horrors subforum wink.png)


I am not sure there is a "general threshold" for portfolios but I think if you sit down for a while and consider how much work project A was and if you think you learnt a lot from it, you'll know whether to put it in your portfolio. Just picture a future employer briefly scanning it and what he would see/think). Also it probably comes with experience - no portfolio is perfect and it's just something we all have to refine as time goes on (especially once you start working on other projects, you may find some of your old stuff obsolete and remove it from your portfolio to make place for something new - remember huge overbloated portfolios are not as effective as concise but well-rounded ones).


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