The innovators in technology have long paved the way for greater social advancement. No one can dispute the fact that the impact of Bill Gates and Microsoft will be far reaching for many years to come. The question is whether or not Microsoft will be able to adapt and thrive in emerging markets. The fact that Microsoft enjoys four decades of establishment also makes it difficult to make major changes without alienating the 1.5 billion Windows users.

This was apparent with the release of Windows 8. Windows users had come to expect a certain amount of consistency from their applications. The Metro tile, touch screen interface left a lot to be desired for enough people that Microsoft eventually more thoroughly implemented an older desktop view minus a traditional Start menu.

The app focused Windows 8 was supposed to be a step towards a greater integration of Cloud technology. In recent years, Microsoft lagged behind its competitors in getting established in new technologies. That includes the billions of dollars the emerging mobile market offered and Cloud computing.

Amazon was the first powerhouse to really establish themselves in the Cloud technology market. Google, Microsoft, and smaller parties are all playing catch up to take a piece of the Cloud pie. More and more businesses are embracing Cloud technology as a way to minimize their equipment and software expenses. While it does take a bit for older businesses to get onboard with such a change, start ups are looking at Cloud computing as an essential part of their business.

But what does that mean for Microsoft? Decisions were made to help update the four decade old Microsoft to the "always on" world we currently live in. Instead of operating in project "silos", different departments were brought together under more generalized headings where they could work closer with one another. Electronic delivery of software, including through Cloud tech, puts Microsoft in the position of needing to meet a pace that is very different from Gates’ early days.

The seriousness of their desire to compete with the likes of Amazon is their pricing matching on Cloud infrastructure services. Microsoft is not a company that has traditionally offered price cuts to compete with others. The fact that they have greatly reduced rates on getting infrastructure set up paves the way for more business users of their Cloud-based apps like Microsoft Office. Inexpensive solutions and free applications open the doors for Microsoft to initiate more sales of other products to their clients.

Former CEO Steve Ballmer recognized there was a need for Microsoft to change directions to remain competitive. In February 2014, he stepped down as CEO stating that the CEO needed to be there through all stages of Microsoft's transition in these more competitive markets. And the former role of his chosen successor, Mr. Satya Nadella? Head of Microsoft's Cloud services division.

Microsoft may not always catch the initial burst of a new development in their space; but they regularly adapt and drive forward. The leadership of Microsoft is clearly thinking forward in what they want to accomplish as sales of PCs have stayed on a continuous decline. It should come as no surprise that Microsoft will embrace this new direction and push towards a greater market share against the likes of Amazon and Google.

Related:

Who Are the Main Players in Big Data?

Is Cloud Computing Safe for Your Business?

Is The Grass Greener in Mobile App Development?

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.

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.