Java still has its place in the world of software development, but is it quickly becoming obsolete by the more dynamically enabled Python programming language? The issue is hotly contested by both sides of the debate. Java experts point out that Java is still being developed with more programmer friendly updates. Python users swear that Java can take up to ten times longer to develop. Managers that need to make the best decision for a company need concrete information so that an informed and rational decision can be made.

First, Java is a static typed language while Python is dynamically typed. Static typed languages require that each variable name must be tied to both a type and an object. Dynamically typed languages only require that a variable name only gets bound to an object. Immediately, this puts Python ahead of the game in terms of productivity since a static typed language requires several elements and can make errors in coding more likely.

Python uses a concise language while Java uses verbose language. Concise language, as the name suggests, gets straight to the point without extra words. Removing additional syntax can greatly reduce the amount of time required to program.  A simple call in Java, such as the ever notorious "Hello, World" requires three several lines of coding while Python requires a single sentence. Java requires the use of checked exceptions. If the exceptions are not caught or thrown out then the code fails to compile. In terms of language, Python certainly has surpassed Java in terms of brevity.

Additionally, while Java's string handling capabilities have improved they haven't yet matched the sophistication of Python's. Web applications rely upon fast load times and extraneous code can increase user wait time. Python optimizes code in ways that Java doesn't, and this can make Python a more efficient language. However, Java does run faster than Python and this can be a significant advantage for programmers using Java. When you factor in the need for a compiler for Java applications the speed factor cancels itself out leaving Python and Java at an impasse.

While a programmer will continue to argue for the language that makes it easiest based on the programmer's current level of knowledge, new software compiled with Python takes less time and provides a simplified coding language that reduces the chance for errors. When things go right, Java works well and there are no problems. However, when errors get introduced into the code, it can become extremely time consuming to locate and correct those errors. Python generally uses less code to begin with and makes it easier and more efficient to work with.

Ultimately, both languages have their own strengths and weaknesses. For creating simple applications, Python provides a simpler and more effective application. Larger applications can benefit from Java and the verbosity of the code actually makes it more compatible with future versions. Python code has been known to break with new releases. Ultimately, Python works best as a type of connecting language to conduct quick and dirty work that would be too intensive when using Java alone. In this sense, Java is a low-level implementation language. While both languages are continuing to develop, it's unlikely that one language will surpass the other for all programming needs in the near future.

One of the biggest challenges faced by senior IT professionals in organizations is the choice of the right software vendor. In the highly competitive enterprise software industry, there are lot of vendors who claim to offer the best software for the problem and it can be really daunting to narrow down the best choice. Additionally, enterprise software costs can often run into millions of dollars thereby leaving very little margin of error. The real cost of choosing a wrong software can often result into losses much more than the cost of the software itself as highlighted by software disasters experienced by leading companies like HP, Nike etc. In such a scenario, senior IT professionals despite years of expertise can find it very difficult to choose the right business software vendor for their organization.

Here are some of the proven ways of short-listing and selecting the right business software vendor for your organization,

·         Understand and Define The Exact Need First: Before embarking on a journey to select the software vendor, it is critical to understand and define the exact problem you want the software to solve. The paramount question to be asked is what business objective does the software need to solve. Is the software required to “reduce costs” or is it to “improve productivity”? Extracting and defining this fundamental question is the bare minimum but necessary step to go searching for the right vendor. It will then form the basis of comparing multiple vendors on this very need that your organization has and will help drive the selection process going forward. The detailed approach involves creating a set of parameters that the software needs to meet in order to be considered. In fact, consider categorizing these parameters further in “must-haves”, “good to have” etc. which will help you assign relevant weights to these parameter and how the software’s fare on each of these parameters

·         Building The List of Vendors Who Meet The Need: Once you have defined your need and distilled that need into various parameters, it’s time to built the list of vendors who you think will meet the need. This is akin to a lead generation model wherein you want to identify a large enough pool and then filters your list down to the best ones. There are multiple ways of building a list of vendors and more often than not, you must use a combination of these methods to build a good enough list.

o   Use Industry Reports: We discussed the IT intelligence offered by leading industry firms Gartner and Forrester in How To Keep On Top Of Latest Trends In Information Technology. These firms based on their access to leading software vendors and CIO network publish vendor comparison research reports across specific verticals as well as specific technologies. Gartner’s Magic Quadrant and Forrester’s Wave are a very good starting point to get an insight into the best software vendors. For example, if you were looking for a CRM solution, you could look for Gartner’s Magic Quadrant for CRM and look at the vendors that make the list. These reports can be pricey but well worth the money if you are going to invest hundreds of thousands in the software. Having said that, you don’t have to trust these report blindly because how these firms define the best software may not match how you define the best software for your organization

o   Competitive Intelligence: If you are a smart professional, you are already keeping tabs of your competition. Chances are that if you are a big organization, you might see a Press Release either from your competitor or their vendor announcing the implementation of new software. Extrapolate that across 5-10 key competitors of yours and you might discover the vendors that your competitors are choosing. This gives you a good indicator that the vendors used by your competitors must be offering something right.

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!