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.

For many people, one of the most exciting and challenging career choices is computer programming. There are several ways that people can enter the computer programming profession; however, the most popular method has traditionally been the educational route through an educational institution of higher learning such as a college or technical school.

Even though many people think of computer programmers as individuals with a technical background, some programmers enter the computer programming profession without a structured technical background. In addition, after further investigation several interesting facts are uncovered when a profile of the best computer programmers is analyzed.

When observing how the top programmers in the profession work, there are four characteristics that tend to separate the top programmers from the average programmers. These four characteristics are:

1.Creativity.
2.Attention To Detail.
3.Learns New Things Quickly.
4.Works Well With Others.

Creativity.

Being a top computer programmer requires a combination of several unique qualities. One of these qualities is creativity. In its very essence, computer programming is about creating programs to accomplish specific tasks in the most efficient manner. The ability to develop computer code to accomplish tasks takes a certain level of creativity. The top computer programmers tend to have a great deal of creativity, and they have the desire to try things in a variety of ways to produce the best results for a particular situation.

Attention To Detail.

While creativity is important for top programmers an almost opposite quality is needed to produce great computer programs on a consistent basis, this quality is attention to detail. The very nature of computer programming requires the need to enter thousands of lines of computer programming code. What separates many top programmers from average programmers is the ability to enter these lines of code with a minimum amount of errors and just as importantly test the code to catch any unseen errors. Top computer programmers have the necessary attention to detail to successfully create and enter the necessary computer code project after project.

Learns New Things Quickly.

The technology field is constantly changing. Almost daily new technology innovations are being developed that require computer programmers to learn new technology or enhancements to current technology on a regular basis. The top computer programmers are able to learn new technology or enhancements quickly, and then they are able to apply what has been learned to their current and future programming projects in a seamless manner.

Works Well With Others.

There are several differences between top computer programmers and other programmers. However, one of the biggest differences is the ability to work well with others. By its very nature, computer programming requires programmers to spend a lot of time alone developing computer code, but the top computer programmers are able to excel at this aspect of computer programming along with being able to work well with other people.

Regarding computer programmers, the top programmers approach and handle their jobs differently than other programmers, and these differences set them apart from the other programmers. For any average programmers who have the desire to excel as a computer programmer, they must understand and embrace the characteristics of top programmers.

Related:

How important is it to exercise for people in technology that sit for hours on end?

What are a few unique pieces of career advice that nobody ever mentions?

Straight up and full disclosure. I'm prejudiced. As a research assignment, the heading is a joke. I'll give you the answer in two words, and then tell you why.

How does HTML 5 compare with flash? Answer: it doesn't.

Lest you think I dislike Adobe's Flash, let's put the cards on the table. I loved Flash. Long before Adobe was Adobe, they had a competitor called Macromedia. Adobe bought that firm. That made my life simpler. I only had to work with one vendor.

Flash was a pretty compelling solution. I used it to mimic operations in Windows to prepare people for the CompTIA exams. The only bugaboo was that dang right-click stuff. A little bit of code from the Microsoft Visual Studio .Net let me flip the left and right mouse buttons so that the right mouse button instead of controlling the Flash player, emulated doing a right-click in the Windows operating system.

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!