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.

Have you ever played a game on your iPhone and wondered how to share it with your friends? Of course, not everyone has iPhones, and they aren’t always watching the leaderboards on the Gaming app, provided by Apple. Well, guess what? You don’t have to take a whole other camera to take a picture of your iPhone to create a photo of that particular score you have achieved. All you have to do is simultaneously press the “Home Button” and the “Lock Button” on your iPhone. After that, your iPhone should consequently flash to white, as if it were snapping its shutter, and taking a picture. Afterwards, you should be able to find the picture in your Photo Albums and share it with your friends.                                                                                        

But, taking screenshots of your iPhone doesn’t always have to deal with your game scores, you can take screenshots of almost any happening on your phone and share it with people! Have you ever had a memorable texting conversation with your friend, where you mistyped something, and the conversation went haywire? Sharing it becomes easy by using this feature. Want to show how odd a website looks on your iPhone compared to looking at it on your computer, and give it to their support to fix it? Take a screenshot of it! The possibilities of this feature are endless, and can become timeless with a simple picture.

Learning SQL development can seem like an overwhelming task at first. However, mastering just a few key points will help ease your way through 80 percent of the day-to-day challenges when writing stored procedures and solving common problems. Here are three important SQL development factors to keep in mind:

Outer Joins
One of the most crucial things to understand in SQL server are joins. Joins are a way to retrieve data from two or more tables based on logical relationships between them. Joins dictate how Microsoft SQL Server ought to use data from one table to select the rows in another table.

In my experience inner joins are intuitive while outer joins can present additional hours of grief by overlooking associations in the other table(s). The outer join is the key to answering questions about what the database does not have. For example, if you need to make a query to display all the students who are without report-cards, you’ll need a left join to get all students coupled with a “where clause” to return the ones who have nulls for their report card table columns in the results.

Many talented Java script programmers have muddled through the SQL Server by deficient coding around the inner join. As a result, their queries can take five hours to run, whereas, properly written left joins, can take only two seconds to run.

Aggregation
Grouping results comes up in SQL a lot more than you might think. Knowing how to write a query when answering questions such as, “What’s the average grade for each teacher’s student list?” is invaluable. This kind of question cannot be answered with a single table or solely by joins.  You’ll often find you need to use joins in conjunction with group by statements. Always write the raw query first and then look at the results. Next, you have to figure out the best way to group them, rewrite your select clause and add a group by clause in the end.

Digging Through Data
I find this is the most lacking skill in many programmers. In fact, many otherwise-talented programmers holding Master’s Degrees fail to get jobs because they couldn’t analyze rows of data objectively during interviews. It’s just something that’s not taught but is crucial to get under you belt. Why? Eventually, some query is not going to perform as you may expect. And, the only way to find discrepancies is to look at rows of data, identify what join isn’t finding a match or where bad data is throwing things into chaos. Get familiar with how joins actually work, even if you have to manually walk through the logic of a large stored procedure’s tree of joins. It’s boring and time-consuming but absolutely necessary.

Take the time to master the core skills that will make you a successful SQL Programmer and avoid queries that run for five hours!

Disruptive technologies such as hand-held devices, cloud computing and social media are rattling the foundations upon which traditional businesses are built. Enterprise customers have grown smarter at ensuring the latest technological trends work in their favor. Everyone is trying to zero in on their core competencies by employing commodity services to run their business.

Likewise, enterprise application vendors need to zero in on their core competencies and enhance more value to the businesses of their clientele by leveraging standards-based commodity services, such as IaaS and PaaS, provided by leaders in those segments (e.g. Amazon EC2, Google Cloud Platform etc.).

What else enterprises need to do is learn to adopt new and emerging technologies such as cloud, utility and social computing to build on them to penetrate new market avenues.

New small and medium-sized entrants into the market are constantly challenging enterprises given their ability to rapidly turnaround and address the requirements of the customers in a cost-effective manner. Additionally, these new advancements also affect how enterprises create, deploy, and manage solutions and applications. If you take the example of Force.com, for instance, you find that it’s a common war zone for enterprise application vendors to furnish SME markets with their applications, with the new entrants mostly having an edge.