My newest project is going to be a 3D Horror Game. I think 3D is the way to go (hello 1995!) these days; it may be harder, but for me at least, simple 2D games just don't interest me, and certainly don't interest my kids who are my main audience. With this in mind I thought a horror game that scares them would be fun.
Here's the very first video. it's just me walking around:-
It's written in Java using the excellent JMonkeyEngine for the 3D. I did have a look at using LibGDX which is also very good. However, for the physics aspect at least, it was just a "leaky" wrapper for Bullet. Bullet is written in C, and so even in Java it seemed to be a case of remembering to dispose of objects and other things I'd hoped to never have to do again.
I've had quite a few Software Developer jobs, been an interviewee even more times, and sometimes even been the interviewer. This is a brief rundown of some tips that I've picked up along the way to avoid wasting both the interviewers and interviewees time, and help you get the right people.
1) Read This
For the love of God, read this before you do any interviews.
2) Be flexible with interview times
...preferrably holding them out of hours. A consciencous interviewee who already has a job doesn't want to risk endangering that job, or waste their holiday allocation, or go through the minefield of taking time of work, if they can help it.
You will make it so much easier for potential recruits if you can do the interview out of hours, or in some way make it as easy as possible for them to get to the interview without disrupting their current job.
3) Test their development skills by getting them to develop something
Software development is about developing software, not about knowing the definition of Dependency Injection or what the definition is of each of the method modifiers available in your chosen language. There is so much to know in Software Development the no single person can know everything, and by asking specific quiz questions, you're turning the interview into a lottery (for both you and the interviewee) where the "winner" is determined by who was lucky enough to have recently read the specific fact that you asked them.
Go through the process of developing software with them. Allow them to use Google and Stack Overflow, and discuss their code as they write it. Allow them to use technologies they are experienced in (or claim to be experienced in). In short, get them to carry out a microcosm of what the actual job would be.
4) Look for Passion
Good software developers love programming, whether it's part of their job or their hobby at home (or anywhere outside their job). I'm always wary of an interviewee who doesn't write code at home. If they do, don't worry or expect that it's actually any good; most hobby development is just for fun, and once it stops being fun it gets abandoned. The fact that they do it is the only important thing.