• 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
ZwodahS

Switching between languages/API

6 posts in this topic

Hi, not really a beginner question but probably fits here than anywhere else.

 

I was coding SFML/C++ for the entire year of 2013, and switched to Libgdx/Java this Jan to port a game I made in C++ to android. After playing with Libgdx for about 2~3 months, + a 1 week break without touching any coding, I faced a problem. I wanted to prepare myself for Ludum dare this week and intended to use SFML/C++ instead of Libgdx, since I like SFML more. I realized I couldn't remember most of my C++/SFML stuffs. (I will probably have to read through my old projects). It is not that I forget the syntax but to do extremely trivial stuffs, like drawing sprite to screen, using my own personal code, or even just loading of assets, I have to reference my old projects to get started.

 

So my question is, what are some ways that you guys do to prevent or reduce this "confusion state" that happens when you switch from one language to another after using one for significant time.  I don't think I am the only one that experience this. Does cheatsheet helps ? I tried creating one in the past but it became extremely tedious and pointless when you are using the language but become extremely useful when you forget them.

 

 

0

Share this post


Link to post
Share on other sites

When I dont spend time on a codebase for a while I will have to read the stuff again and see how I do things, this is normal you can't keep all of this in your head all the time. The thing is though that you haven't actually forgotten how something works it's just the details that you miss, once you have seen them again for once you remember how it works.

 

I switch between 3 programming languages often, mostly C++/C# the only mistake I always make is array syntax related, if I switch to or from python extra {} are added in python or forgotten in C++.

2

Share this post


Link to post
Share on other sites

I usually keep a document with the most important stuff I've done in some project, for each project. Most doubts I faced during the development should be there, also tricky workarounds I've used and whatever I think I'm going to forget about soon. It's good to keep it neat and simple.

 

Quite of a simple thing, but most people get lazy to do it and I find it very helpful.

1

Share this post


Link to post
Share on other sites

Descriptive documentation, commenting (in code, perhaps within mainly a version of the game source code only for that), and to continue using the previous language and your libraries as much as you can while working another - is about all that you can do.  

 

Long term, if you revisit coding issues enough times then most of them will stick more, which might take years.

 

This thread shows the importance of making sure to thoroughly complete a game (or version of one) before moving to another project when possible. Read my signature below here and you will see that I am adamant about these matters.

0

Share this post


Link to post
Share on other sites

I have read through some of my completed projects since I posted this :D. Most of the memory came back after a while =).

 

I think having completed projects helps a lot. I wanted to make a cheatsheet for this a few years ago when I was switching between python / java / C# but I guess once you have enough projects in that language, they will serve the purpose of the cheatsheet.

0

Share this post


Link to post
Share on other sites

I regularly switch between several languages and APIs. For the languages I use the most (C, C++, C#, Java, JavaScript, PHP, Python, and Haskell) I have a quick reference sheet that has some of the common techniques and styles that are specific or noteworthy to that language. For APIs, I also have references for some of my more commonly used methods or classes in some of my regularly used APIs. I also have at least 1 book for each language or API (if there is a book for it) nearby so I can pull it out and use it if my quick reference sheet doesn't provide enough detail.

 

I also like to comment my code regularly, especially when using 3rd-party libraries.

 

Plus there's always the internet and I have a bookmarks folder for all the reference pages for just about every API I use regularly.

1

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