One of the most recent updates to the iPhone, and more specifically the operating system that is packaged with the iPhone, iOS, brought one of the most fantastic and phenomenal updates ever: an update to Maps. Maps has been used as an application that provides an easy way to find routes, and (obviously) maps about certain areas, businesses in the local vicinity, and also leaving pins on favorited locations, or pins where you have explored, and for many other reasons. However, although Maps has always been a great way to travel with, it has always been redundant to travel with, also. When you used Maps a while ago, you had to route your map, and then manually click each next button as you reached each turn or freeway exit, and the like. So, if you had to turn left on a certain street, you had to tell your phone you had done so, so it would give you the next directions. As a result, it could become very dangerous to always have your phone out, looking at it, while you are on a high-speed freeway. But, the newest update solved that, and brought a great amount of new features.

Using Maps GPS

Using Maps is as easy as it gets. Most of the time, when you are using Maps, you are using it to search for a location, and finding a way to get there. To start off, let’s search for the nearest mall, and routes to get there. Simply search a nearby mall you know about, or search the general word “mall” by tapping on the top text box, and typing in mall, and searching. Pins will drop down on the screen, and locating the mall by zooming into certain streets and locations will help you find the mall you want. Once you find the mall you desire to go to, click on the blue arrow, and scroll down, and tap on the button that says “Directions To Here.”

As a result of tapping on that particular button, a new window should show up asking where your starting location is. On default, this location is your current location; if it is anything else, simply type in the starting location into the top address bar, such as your house. Once you are ready to go, tap on route, and you should be ready to go. Well, not exactly. One of the best features that has been implemented in the new system is suggested routes, and alternative routes. If you don’t like to drive on certain streets, or roads, the system provides you with different methods to get to your destination, which may avoid a road you don’t feel like driving on that certain day, or time, or you simply don’t want to take the freeway. It’s all okay, as Maps provides you with many different routes to take. Once you find the route you want (by tapping on the certain route’s outline), click start, and you should be ready to go. Make sure you turn up your volume so you can hear the directions!

Maps for Alternative Transportation

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.

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!