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.

The job market is extremely tight these days, with several qualified workers being available for each empty position. That means that should you find yourself looking for work, for whatever reason, you need to make sure your interview skills are up to snuff. We will be taking a look at a variety of different tips that will help ensure your success during the interview process, including how to make sure your employers know about your C training experience. Here are some others:

• Do your own research in advance – Before you even step through the doorway to initiate the application process with a company, you should already know quite a bit about it. Investigate the corporate culture, speak with contacts who have experience with the firm, or search online; however you do it, having as much information as possible can really help you get an advantage during the hiring process. If you have specific experience, such as C training, that is of exceptional value to the firm you are applying to you can market yourself more effectively to the hiring agent.
• Dress Appropriately – In a perfect world, programming skill and experience such as C training should be the only factors in consideration when looking at a prospective hire; in real life this is often not the case. Don’t miss out because you gave a bad impression to someone, and strive to look your absolute best during your job interview. It is unfortunate, but the IT industry in particular tends to have a reputation for lacking in this department, so breaking the mold can be of great benefit to you.
• Be ready to interview at all times – You may be surprised how often job candidates are asked to participate in an off-the-cuff phone interview on the spot. Same-day in person interviews also are rising in popularity. Make sure you are always able to respond quickly if these situations come up and you get a fast interview. Memorize a few points in advance you can use to pump yourself up, such as an anecdote about your C training or other particular skills you may possess.

Job interviews are notoriously stressful for many people. Using simple tips like these can help you to prepare in advance for situations you may encounter during the interview process, and help you ultimately secure that new job. Make sure to emphasize whatever makes you special as an individual, such as your extensive C training.

The importance of variables in any programming language can’t be emphasised enough. Even if you are a novice, the chances are good that you will have been using variables for quite a while now.

They are the cornerstone of any language and without them we would not be able to accomplish much of anything. However, most of you up until this point have probably only been working with standard variables, variables which can hold single values such as an integer, a single character, or a string of text.

In this tutorial we are going to take a look at a more special type of variable called an array. Arrays can seem quite daunting at first glance but once you get used to working with them you will wonder how you ever managed to program without them.

The reason arrays are special is because they can hold more than one value. Think about this: say you create a variable which contains a line of text like the code below:

The Zen of Python, by Tim Peters has been adopted by many as a model summary manual of python's philosophy.  Though these statements should be considered more as guideline and not mandatory rules, developers worldwide find the poem to be on a solid guiding ground.

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!