We're beginning a new series talking about breaking down game mechanics into bite-sized pieces that you can think about and implement on your own.

I was talking to a close friend about their interview skills and the fact that they never make it past the interview stages and receive an offer for a job. The issue that we talk about is the simple fact that you need to work hard on your self-growth and really improve your interview and technical skills. If that means you stop playing games all week, then that's what you need to do. If you need to focus and you can't do it at home, then go to the library or a coffee shop. The moral of the story is that you need to be serious about your career and if you want something, then don't expect it to fall in your lap. Instead, work for that thing you want. The only way you can do it is by dedicating the time and effort to learn and self-improve.

If you haven't subscribed to the Journey To Programming blog, then check it out here:

http://www.journeytoprogramming.com

This is a common question in forums and among many students that I interacted with while teaching the last few years.

Should you start programming with GameMaker Studio, Unity3D, or Unreal Engine?

There are advantages to each of the above mentioned engines, but in all honesty you should learn to program with the language or tool that best motivates you to continue programming.

If you want to be a game developer and therefore only will accept using a game engine, then that's fine. My recommendation is to learning the fundamentals of programming and game development using Unity3D rather than the other two options. Unity has excellent tutorials and a huge support community that you will be able to use during your learning. But, the primary reasoning is that I believe Unity will force you to get closer to coding.

If you are looking to learn how to program and are not attached to game engines, then I highly recommend jumping into a language like Python or C# and follow tutorials on Youtube or some of the many blogs and forums out there. Follow tutorials to build tangible programs and software, and then modify them slightly with the skills your develop.

The skills learned in the development process will be all around beneficial.

Good luck and have fun.

Remember to subscribe to the channel!

If you haven't subscribed to the Journey To Programming blog, then check it out here:

http://www.journeytoprogramming.com

So, yes I've moved to the Boston area to take on a roll with a production studio that develops interactive experiences.

It's been one heck of an experience and so far Boston has been great.

From here on I want to get new content made for you guys. I'm looking at providing technical content, job search advice, and business information.

I'd prefer you guys learn from my mistakes and take the information I've learned over the years to use to your advantage.

Make sure to subscribe to the channel and join the blog at www.journeytoprogramming.com

It's been a while since our last post and we really want to get you some new great content. So, here's what's been going on.

If you haven't subscribed to the Journey To Programming blog, then check it out here:

http://www.journeytoprogramming.com

So, it's been a while since my last update on what's been going on. I like to keep our community updated on my happenings and the last time I did one of these was probably in 2017. So, it's an overdue update.

In summary, I've been focused on my company for the last couple of years. The main goal is to grow the company, and it's been one heck of a ride with bumps, hills, and mountains along the way.

Lately, we've been working on some great workplace simulation geared towards providing incoming employees with a method to acquaint themselves with their new work environment prior to getting on site to the job. This allows for them to be for efficient right away by instilling confidence in knowing there setting so that it's not just another cognitive burden.

If you haven't subscribed to the Journey To Programming blog, then check it out here:

http://www.journeytoprogramming.com

Hey guys, while I was working at a local coffee shop I struck up a conversation with someone and they told me about their troubles getting a programming job. I asked them about what their experience has been in the industry and then to tell me the process they've gone about in their efforts to apply for jobs. That conversation has converted into this response:

Hey guys, while I was working at a local coffee shop I struck up a conversation with someone and they told me about their troubles getting a programming job. I asked them about what their experience has been in the industry and then to tell me the process they've gone about in their efforts to apply for jobs. That conversation has converted into this response:

Hey guys, while I was working at a local coffee shop I struck up a conversation with someone and they told me about their troubles getting a programming job. I asked them about what their experience has been in the industry and then to tell me the process they've gone about in their efforts to apply for jobs. That conversation has converted into this response:

Here's a short talk about the technical process of having computers communicate over the network with each other. In this talk we discuss a use case of having a motion detector notify another computer when someone triggers the motion detection.