Many individuals are looking to break into a video game designing career, and it's no surprise. A $9 billion industry, the video game designing business has appeal to gamers and non-gamers alike. High salaries and high rates of job satisfaction are typical in the field.

In order to design video games, however, you need a certain skill set. Computer programming is first on the list. While games are made using almost all languages, the most popular programming language for video games is C++, because of its object-oriented nature and because it compiles to binary. The next most popular languages for games are C and Java, but others such as C# and assembly language are also used. A strong background in math is usually required to learn these languages. Individuals wishing to design games should also have an extensive knowledge of both PCs and Macs.

There are many colleges and universities that offer classes not only in programming but also classes specifically on game design. Some of these schools have alliances with game developing companies, leading to jobs for students upon graduation. Programming video games can be lucrative. The average game designer's salary is $62,500, with $55,000 at the low end and $85,000 at the high end.

Programmers are not the only individuals needed to make a video game, however. There are multiple career paths within the gaming industry, including specialists in audio, design, production, visual arts and business.

Designing a video game can be an long, expensive process. The average budget for a modern multiplatform video game is $18-$28 million, with some high-profile games costing as much as $40 million. Making the game, from conception to sale, can take several months to several years. Some games have taken a notoriously long time to make; for example, 3D Realms' Duke Nukem Forever was announced in April 1997 and did not make it to shelves until July 2011.

Video game programmers have a high level of job satisfaction. In a March 2013 survey conducted by Game Developer magazine, 29 percent of game programmers were very satisfied with their jobs, and 39 percent were somewhat satisfied.

If you're interested in a game development career, now's the time to get moving. Take advantage of the many online resources available regarding these careers and start learning right away.

This section of our beginning python training class always stumps students.  Firstly, because they need to know the difference between a function and a method.  Secondly, they need to understand object oriented programming concepts.  Thirdly, they need to realize that python has three types of methods.  Then they need to know how to use each method, which means they need to know the purpose of each method type.  Then they have to understand mutable versus non-mutable types.  The list goes on.  As part of our python tutorial, I hope to shed some light on this confusing topic.

To begin, the difference between a function and a method in python is that a method is defined within a class.  Here is an illustration:

#function

	def greeting():
	                print "Hello, I hope you're having a great day!"

	class HSGPrinter(object):
	                #method
	                def greeting(self): 
	                                print "Hello, I hope you're having a great day!"

As should be obvious, the second definition of greeting is encapsulated within the HSGPrinter class and is , therefore, refered to as a method.

The astute reader will notice that the greeting method contains one parameter named self.  For those who know C++ , Java or C#, self is equivalent to this i.e. it is a reference to the invoking object:

How Can Managers Work More Efficiently with IT?

Would you rather work under someone who is an excellent developer but lacks people skills or leadership capabilities - or for someone that has excellent people skills, communicates well, and is a great leader but has limited understanding of productive coding practices? That’s not to say that the choice is one or the other but in many professional situations it does.

Managing an IT staff comes with numerous challenges, especially if the manager has no previous experience with the coding necessary for completing the project. Managing a business and IT's execution of tasks vary greatly in required skill sets, but it's important to find a cohesive and cooperative middle ground in order to see a project to its end. To fully grasp the intricacies of IT's involvement in the project at hand, managers can do the following to help further their efforts.

Get a basic understanding of coding and technical practices necessary for the project at hand by taking the time to research and practice enough to get a grip on the concept. This will allow managers insight on what their IT folks are really working on daily. Expertise in a programming language is not required, only an overview of the stuff that matters, i.e. understanding the concept of OOP (Object Oriented Programming.) Having this knowledge cannot be overlooked and will gain respect among multiple spectrums in the organization.

It’s the eternal conundrum of a hiring manager – you have to hire for every single position in the company without any first-hand experience. How to do it? If you can have a trusted programmer sit in on the interview, that’s ideal, of course. But what if you’re hiring your first programmer? Or what if you’re hiring a freelancer? Or what if company policy dictates that you’re the only person allowed to do the interviewing? Well, in that case, you need some helpful advice and your innate bullshit detector. We questioned programmers and hiring managers and compiled a list of dos and don’ts. Here are some things to ask when interviewing programmers:

Past Experience

Ask the programmer about the biggest disaster of his career so far, and how he handled it. Did he come in at midnight to fix the code? Was he unaware of the problem until someone brought it up? Did someone else handle it?  According to our programmer sources, “Anyone worth their salt has caused a major meltdown. If they say they haven’t, they’re lying. Or very, very green.” Pushing a code with bugs in it isn’t necessarily bad. Not handling it well is bad.

As usual, your biggest asset is not knowing the field, it is knowing people. Asking about career disasters can be uncomfortable, but if the interviewee is experienced and honest then she won’t have a problem telling you about it, and you will get an idea of how she handles mishaps. Even if you don’t understand what the disaster was or how it was fixed, you should be able to tell how honest she’s being and how she handles being put on the spot.