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.

As much as we love to assume free Wi-Fi is secure, this is far from the truth. Because you are attaching to a service many others are connected to as well, without security measures, your device can be hacked, especially if the network is unencrypted. Because this encryption involves handing out a 26-character hexadecimal key to every individual wanting to use that network, most places opt for ease of access over security. And even with a secure network, your information is vulnerable to everyone else who has the password and is on the network.

This may not seem like such a big deal and many people don’t believe they have anything to hide on their personal devices, but remember what you use on those devices. Chances are your e-mail is attached as well as all other social media sites. You may have apps that track your finances or private messages to certain others that you would never want anyone else to see. Luckily, there are steps that can be taken to reduce and prevent any unwanted information grabbers from accessing your personal information.

To start, go through your computer’s settings in order to verify your operating system’s security functions are all set to offer the highest protection. Open up the Control Panel and double check that your Firewall is enabled for both private and public networks. Then, go to Network and Sharing to open Change advanced sharing settings. In here, you can turn off file and printer sharing and network discovery for public networks.

One of the most important things to watch for is HTTPS. Hypertext Transfer Protocol Secure ensures secure communication across the web. Many of the major email systems use this when you log in (as another layer of password protection) but drop the security as soon as the login is complete. To keep this going, HTTPS Everywhere is a browser extension that gives you a secure connection when browsing some of the more popular sites. It can also be programmed for other sites you like to visit that don’t use HTTPS.

Not every place on the internet provides the choice of HTTPS, and VPNs are there to fill in the security gap. Virtual Private Networks allows data to be sent and received through public access points as if it were directly connected to a secure network. Many businesses offer this for company devices, but if you are an individual looking for that kind of security, ProXPN is a free version that can be upgraded. Unfortunately, it limits your speed, but other choices include VPNBook, OpenVPN Shield Exchange, and OkayFreedom.

With these three steps implemented, secure public Wi-Fi can be achieved. No longer will you have to worry about connecting in an unsure environment with strangers, never knowing if your information is being stolen. With all of the options free of charge, it is also an affordable means of protecting yourself that only takes a little time and effort to implement and guarantee safety.

In Demand IT Skills

Password Management Tools

Net Neutrality for the Layperson

What are a few unique pieces of career advice that nobody ever mentions?

When businesses are trying to expand and require professionals to lead teams, terminology may get in the way of who performs what roles. When it comes to information technology (IT), new and vital professionals may seem hard to differentiate between one another. However, there are key differences between specific professionals needed with IT departments. Here are the responsibilities that differentiate between an IT manager and an IT project manager.

IT Managers

IT managers are the leaders of the entire IT infrastructure a business has to function properly. The IT manager must lead the entire IT department to regulate and maintain the IT network for the business. As a manager, this IT professional corresponds with other departments in the business about how the IT department is implementing the goals the business is aiming toward. In addition, the manager must be fiscally responsible and answer to executives and financial officers in the business the reasons behind certain costs and investments. Because of the dual computer technology and business acumen this profession requires, many IT managers have a Master of Business Administration (MBA) related to information technology.

IT Project Managers

The Zen of Python, by Tim Peters has been adopted by many as a model summary manual of python's philosophy.  Though these statements should be considered more as guideline and not mandatory rules, developers worldwide find the poem to be on a solid guiding ground.

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!