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.

In recent decades, companies have become remarkably different than what they were in the past. The formal hierarchies through which support staff rose towards management positions are largely extinct. Offices are flat and open-plan collaborations between individuals with varying talent who may not ever physically occupy a corporate workspace. Many employed by companies today work from laptops nomadically instead. No one could complain that IT innovation hasn’t been profitable. It’s an industry that is forecasted to rake in $351 billion in 2018, according to recent statistics from the Consumer Technology Association (CTA). A leadership dilemma for mid-level IT managers in particular, however, has developed. Being in the middle has always been a professional gray area that only the most driven leverage towards successful outcomes for themselves professionally, but mid-level managers in IT need to develop key skills in order to drive the level of growth that the fast paced companies who employ them need. 

What is a middle manager’s role exactly? 

A typical middle manager in the IT industry is usually someone who has risen up the ranks from a technical related position due to their ability to envision a big picture of what’s required to drive projects forward. A successful middle manager is able to create cohesion across different areas of the company so that projects can be successfully completed. They’re also someone with the focus necessary to track the progress of complex processes and drive them forward at a fast pace as well as ensure that outcomes meet or exceed expectations.

What challenges do middle managers face in being successful in the IT industry today? 

While middle managers are responsible for the teams they oversee to reach key milestones in the life cycle of important projects, they struggle to assert their power to influence closure. Navigating the space between higher-ups and atomized work forces is no easy thing, especially now that workforces often consist of freelancers with unprecedented independence. 

What are the skills most needed for an IT manager to be effective? 

Being educated on a steady basis to handle the constant evolution of tech is absolutely essential if a middle manager expects to thrive professionally in a culture so knowledge oriented that evolves at such a rapid pace. A middle manager who doesn't talk the talk of support roles or understand the nuts and bolts of a project they’re in charge of reaching completion will not be able to catch errors or suggest adequate solutions when needed. 

How has the concept of middle management changed? 

Middle managers were basically once perceived of as supervisors who motivated and rewarded staff towards meeting goals. They coached. They toggled back and forth between the teams they watched over and upper management in an effort to keep everyone on the same page. It could be said that many got stuck between the lower and upper tier of their companies in doing so. While companies have always had to be result-oriented to be profitable, there’s a much higher expectation for what that means in the IT industry. Future mid-level managers will have to have the same skills as those whose performance they're tracking so they can determine if projects are being executed effectively. They also need to be able to know what new hires that are being on-boarded should know to get up to speed quickly, and that’s just a thumbnail sketch because IT companies are driven forward by skills that are not easy to master and demand constant rejuvenation in the form of education and training. It’s absolutely necessary for those responsible for teams that bring products and services to market to have similar skills in order to truly determine if they’re being deployed well. There’s a growing call for mid-level managers to receive more comprehensive leadership training as well, however. There’s a perception that upper and lower level managers have traditionally been given more attention than managers in the middle. Some say that better prepped middle managers make more valuable successors to higher management roles. That would be a great happy ending, but a growing number of companies in India’s tech sector complain that mid-level managers have lost their relevance in the scheme of the brave new world of IT and may soon be obsolete.

Although reports made in May 2010 indicate that Android had outsold Apple iPhones, more recent and current reports of the 2^nd quarter of 2011 made by National Purchase Diary (NPD) on Mobile Phone Track service, which listed the top five selling smartphones in the United States for the months of April-June of 2011, indicate that Apple's iPhone 4 and iPhone 3GS outsold other Android phones on the market in the U. S. for the third calendar quarter of 2011. This was true for the previous quarter of the same year; The iPhone 4 held the top spot.  The fact that the iPhone 4 claimed top spot does not come as a surprise to the analysts; rather, it is a testament to them of how well the iPhone is revered among consumers. The iPhone 3GS, which came out in 2009 outsold newer Android phones with higher screen resolutions and more processing power. The list of the five top selling smartphones is depicted below:

1. Apple iPhone 4
2. Apple iPhone 3GS
3. HTC EVO 4G
4. Motorola Droid 3
5. Samsung Intensity II[1]

Apple’s iPhone also outsold Android devices7.8:1 at AT&T’s corporate retail stores in December. A source inside the Apple company told The Mac Observer that those stores sold some 981,000 iPhones between December 1st and December 27^th 2011, and that the Apple device accounted for some 66% of all device sales during that period (see the pie figure below) . Android devices, on the other hand, accounted for just 8.5% of sales during the same period.

According to the report, AT&T sold approximately 981,000 iPhones through AT&T corporate stores in the first 27 days of December, 2011 while 126,000 Android devices were sold during the same period. Even the basic flip and slider phones did better than Android, with 128,000 units sold.[2] However, it is important to understand that this is a report for one particular environment at a particular period in time. As the first iPhone carrier in the world, AT&T has been the dominant iPhone carrier in the U.S. since day one, and AT&T has consistently claimed that the iPhone is its best selling device.

Chart courtesy of Mac Observer: http://www.macobserver.com/tmo/article/iphone_crushes_android_at_att_corporate_stores_in_december/

A more recent report posted in ismashphone.com, dated January 25 2012, indicated that Apple sold 37 million iPhones in Q4 2011.  It appears that the iPhone 4S really helped take Apple’s handset past competing Android phones. According to research firm Kantar Worldpanel ComTech, Apple’s U.S. smartphone marketshare has doubled to 44.9 percent.[3] Meanwhile, Android marketshare in the U.S. dropped slightly to 44.8 percent. This report means that the iPhone has edged just a little bit past Android in U.S. marketshare. This is occurred after Apple’s Q1 2012 conference call, which saw themselling 37 million handsets. Meanwhile, it’s reported that marketers of Android devices, such as Motorola Mobility, HTC and Sony Ericsson saw drops this quarter.

Static variables in Python are created as part of the class declaration.  By contrast, instance variables are created as part of a regular method and not a classmethod or staticmethod.

class A:
  i=3  # static variable
	
  def dosomethingregularmethod(self):
       self.k=4   # instance variable
	
# to access static variables


A.i