The short answer is, yes and no. It depends upon who you are. The purpose of this entry is to help you determine, yes or no.

Full disclosure. This entry is created on a Mac mini. And doing so on Windows 8 (Release Preview). If you are a developer, in my humble opinion you need to test on all platforms you expect your app to run or you are not much of a developer.

To be successful you need to leave politics in geographical territory known as Washington DC. My definition of that is: 14 mi.² of real estate surrounded by reality.

Only in politics can we afford to take sides. Those of us in IT, especially developers need to do our best to be all things to all people. Certainly this is a technical impossibility. However in our game we can get some points for at least being serviceable if not outstanding.

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!

Back in the late 90's, there were a number of computer scienctists claiming to know java in hopes of landing a job for $80k+/year.  In fact, I know a woman you did just that:  land a project management position with a large telecom and have no experience whatsoever.  I guess the company figured that some talent was better than no talent and that, with some time and training, she would be productive.  Like all gravey train stories, that one, too, had an end.  After only a year, she was given a pink slip.

Not only are those days over, job prospects for the IT professional have become considerably more demanding.  Saying you know java today is like saying you know that you have expertise with the computer mouse; that's nice, but what else can you do.   This demand can be attributed to an increase in global competition along with the introduction of a number of varied technologies.   Take .NET, Python, Ruby, Spring, Hibernate ... as an example;  most of them, along with many others, are the backbone of the IT infrastructure of most mid-to-large scale US corporations.  Imagine the difficulty in finding the right mix of experience, knowledge and talent to support, maintain and devlop with such desparate technologies.

Well imagine no more.  According to the IT Hiring Index and Skills Report, seventy percent of CIO’s said it's challenging to find skilled professionals today.  If we add the rapid rate of technological innovation into the mix of factors affecting more businesses now than ever before, it’s understandable that the skill gap is widening.  Consider this as well:  the economic downturn has forced many potential retires to remain in the workforce.  This is detailed in MetLife's annual Study of Employee Benefits which states that“more than one-third of surveyed Baby Boomers (35%) say that as a result of economic conditions they plan to postpone their retirement.”  How then does the corporation hire new, more informed/better educated talent?    Indeed, the IT skills gap is ever widening.

In order to compensate for these skill discrepencies, many firms have resorted to hire the ideal candidates by demanding they possess a christmas wish list of expertise in a variety of different IT disciplines.  It would not be uncommon that such individuals have a strong programming background and are brilliant DBA's.  What about training?  That is certainly a way to diminish the skills gap.

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.