Once again Java tops C as the number one sought after programming language on the internet.  According TIOBE Programming Community Index for February 2013 and five search engines: Google, Bing, Yahoo!, Wikipedia, Amazon, YouTube and Baidu, Java regained its position after being bumped by C in May 2012.

Despite the recent urging by the U.S. Department of Homeland Security of computer users to disable or uninstall Java due to a flaw in Runtime Environment (JRE) 7, Java, has increased its market share of all languages by (+2.03%) in the past six months. The jump in Java’s popularity does not come as a surprise as the Android OS claims massive success in the mobile space.  The top twelve programming languages listed in the index are:

1.  Java
2.  C
3.  Objective-C 
4.  C++
5.  C#
6.  PHP
7.  Python
8.  (Visual) Basic
9.  Perl
10.  Ruby
11. Java Script
12. Visual Basic.NET

Also rising, Python and PHP which are competing to becoming the most popular interpreted language.

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.

In most business circles, the question of whether or not a website truly helps a company's business has become somewhat moot. Simply put, a website is a necessary evil, like it or not. The question is no longer, should a company have a website, but rather, is the website optimized to ensure the best potential results. Of course, it is important to understand what is meant by "helping a company."

Many businesses are under the assumption that a website is going to turn into cold hard cash for the company. Well, that could be the case if the organization is using a type of e-commerce platform to buy and sell goods. Many businesses are service oriented and as such, the website serves an entirely different purpose.

Jeff Nelson, a former Googler and inventor of Chromebook says on Quora, “One habit I've clung to is writing small prototypes when I'm trying to learn new concepts.
For example, I'll sit down with a book or a web page, and over the course of a few hours, write 30 or 40 programs all of them only a few dozen lines long.  Each program intended to demonstrate some simple concept. This prototyping makes it very easy to try out many concepts in a short period of time.”

Miguel Paraz, Software Engineering Student habit is to “keep a log in a text file or document on my work computer. Before trying to solve a problem, I write it down first. And then I describe the details as they happen.”