The earning potential of a software developer largely depends on their knowledge, their chosen area of expertise, experience and flexibility to relocate if necessary.  In the ever changing landscape of Information Technology, many argue that the way to make more money is to specialize in a technology that fewer people are using.  As an example, there are tons of Java programmers out there, but nowhere near enough in lesser known languages such as Perl or Python.  However, there are plenty of opportunities for folks who are willing to burn the midnight oil to gain skills in these niche disciplines.

Because the Information Technology Industry is a rapidly evolving entity, gunning for the "Next Big Thing" is constantly an arm’s length away.  For this reason, developers looking to get requisite knowledge to successfully compete can, for the most part, expect to resign their weekends for the LOVE of code and studying.   And, it’s fair to say that a stick-to-itiveness to teach yourself how to code can be more important than any degree when job prospecting.  Sam Nichols, a mobile developer at SmugMug, puts it this way: “Build a table, build a computer, build a water gun, build a beer bong, build things that will take a week and build things that need to be done in 40 minutes before the party. Making stuff is what this field is all about and getting experience building things, especially with others, especially when it breaks and fails along the way can help with perspective and resiliency.”

Software developers already skilled at writing code are readily able to translate that knowledge to web development. The fact that the information technology sector has shifted largely to web-based infrastructure and software application as system (SaaS) database and operating system capabilities, means that software developers have a wide variety of opportunity in the web development segment of the consulting and job market.

If you are a software developer seeking to increase your earning potential, gaining expertise in  Web development  enhances your ability to attract new opportunities. The more creative a software developer, the far better chance they will have at benefitting from current market demand for new technologies and software innovation. Customization is hot right now, and software developers involved in the creation of updates and unique features to SaaS can add extra value to their portfolio with very little time and effort involved.

 In order for software developers to stay abreast of their field, continuing education and is required to ensure that technical skills are up-to-date. Gaining knowledge in design of computer applications is one of the main objectives in the development and planning of software products.
Once adequate knowledge has been acquired, many software developers can use those insights to develop custom software for a client as a consultant.

Companies have been collecting and analyzing data forever, pretty much.” So what’s really new here? What’s driving the data-analytics revolution and what does it mean for those that choose to postpone or ignore the pivotal role big-data is currently having on productivity and competition globally?

General Electric chairman and CEO Jeff Immelt explains it best when stating that “industrial companies are now in the information business—whether they like it or not.”  Likewise, digital data is now everywhere, it’s in every industry, in every economy, in every organization and according to the McKinsey Global Institute (MGI), this topic might once have concerned only a few data geeks, but big data is now relevant for leaders across every sector as well as consumers of products and services.

In light of the new data-driven global landscape and rapid technological advances, the question for senior leaders in companies now is how to integrate new capabilities into their operations and strategies—and position themselves globally where analytics can influence entire industries. An interesting discussion with six of theses senior leaders is covered in MGI’s article, “How companies are using big data and analytics,” providing us with a glimpse into a real-time decision making processes.

I suspect that many of you are familiar with the term "hard coding a value" whereby the age of an individual or their location is written into the condition (or action) of a business rule (in this case) as shown below:

if customer.age > 21 and customer.city == 'denver'

then ...

Such coding practices are perfectly expectable provided that the conditional values, age and city, never change. They become entirely unacceptable if a need for different values could be anticipated. A classic example of where this practice occurred that caused considerable heartache in the IT industry was the Y2K issue where dates were updated using only the last 2 digits of a four digit number because the first 2 digits were hard-coded to 19 i.e. 1998, 1999. All was well provided that the date did not advance to a time beyond the 1900’s since no one could be certain of what would happen when the millennia arrived (2000). A considerably amount of work (albeit boring) and money, approximately $200 billion, went into revising systems by way of software rewrites and computer chip replacements in order to thwart any detrimental outcomes. It is obvious how a simple change or an assumption can have sweeping consequences.

You may wonder what Y2K has to do with Business Rule Management Systems (BRMS). Well, what if we considered rules themselves to be hard-coded. If we were to write 100s of rules in Java, .NET or whatever language that only worked for a given scenario or assumption, would that not constitute hard-coded logic? By hard-coded, we obviously mean compiled. For example, if a credit card company has a variety of bonus campaigns, each with their own unique list of rules that may change within a week’s time, what would be the most effective way of writing software to deal with these responsibilities?

Millions of people experienced the frustration and failures of the Obamacare website when it first launched. Because the code for the back end is not open source, the exact technicalities of the initial failings are tricky to determine. Many curious programmers and web designers have had time to examine the open source coding on the front end, however, leading to reasonable conclusions about the nature of the overall difficulties.

Lack of End to End Collaboration
The website was developed with multiple contractors for the front-end and back-end functions. The site also needed to be integrated with insurance companies, IRS servers, Homeland Security servers, and the Department of Veterans Affairs, all of whom had their own legacy systems. The large number of parties involved and the complex nature of the various components naturally complicated the testing and integration of each portion of the project.

The errors displayed, and occasionally the lack thereof, indicated an absence of coordination between the parties developing the separate components. A failed sign up attempt, for instance, often resulted in a page that displayed the header but had no content or failure message. A look at end user requests revealed that the database was unavailable. Clearly, the coding for the front end did not include errors for failures on the back end.

Bloat and the Abundance of Minor Issues
Obviously, numerous bugs were also an issue. The system required users to create passwords that included numbers, for example, but failed to disclose that on the form and in subsequent failure messages, leaving users baffled. In another issue, one of the pages intended to ask users to please wait or call instead, but the message and the phone information were accidentally commented out in the code.

While the front-end design has been cleared of blame for the most serious failures, bloat in the code did contribute to the early difficulties users experienced. The site design was heavy with Javascript and CSS files, and it was peppered with small coding errors that became particularly troublesome when users faced bottlenecks in traffic. Frequent typos throughout the code proved to be an additional embarrassment and were another indication of a troubled development process.

NoSQL Database
The NoSQL database is intended to allow for scalability and flexibility in the architecture of projects that will use it. This made NoSQL a logical choice for the health insurance exchange website. The newness of the technology, however, means personnel with expertise can be elusive. Database-related missteps were more likely the result of a lack of experienced administrators than with the technology itself. The choice of the NoSQL database was thus another complication in the development, but did not itself cause the failures.

Another factor of consequence is that the website was built with both agile and waterfall methodology elements. With agile methods for the front end and the waterfall methodology for the back end, streamlining was naturally going to suffer further difficulties. The disparate contractors, varied methods of software development, and an unrealistically short project time line all contributed to the coding failures of the website.