One of the most significant developments of mankind has been the art of writing. The earliest type of writing was in the form of graffiti and paintings on rocks and walls of caves. The first people who engaged in writing are reported to have been Sumerians and the Egyptians around 3500-3200 BC.[i] Early writing of this type was in the form of cuneiform and hieroglyphics. After that, writing emerged in different styles and form per the different societies and differences in expression.

Words are magical. They have preserved records of civilizations. They express desires and dreams and thoughts. But why write at all? What was or is the motive for writing? People write for different reasons. Some write because they have something to say; something to share with others, to inform. Others write to share their feelings.

George Orwell claimed there are four main reasons why people write as depicted below:

·         Sheer Egoism: According to this concept, people write because they want to be talked about; they want to reveal their cleverness. People who are motivated by sheer egoism desire to be counted among the top crust of humanity such as scientists, artists, politicians, lawyers and successful businessmen who are always putting their thoughts in print.

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.

 Unlike traditional online courses that charge a fee, limit enrollment and provide credit or certification, Moocs (massive open online courses) are usually free or low cost and can host hundreds of  thousands global participants.  Although MOOC have been around for years in the form of collective techie learning gatherings, participation in 2012 has ballooned at a rapid pace likened to FaceBook in its heyday.  According to The Year of the MOOCarticle in the New YorkTimes, edX, a nonprofit start-up backed by Harvard and MIT, had 370,000 registrants in the fall of its first official courses. This paled in comparison to the amount of students that Courseraattained in its first year of online learning opportunities, 1.7 million!

Will MOOCs Replace education as we know it?

Like any new trend, massive participation in online classes has its challenges. Lynda Weinman has ample experience when pointing out that they are by no means a replacement for formal education.  As a former digital animator, special effects designer and classroom college teacher, Linda paved the path for an earlier version of MOOC education in the mid 90’s when she founded Lynda.comas an aide to her own students. Over four million students and 2,200 courses later she’s confident when clarifying that many of the collegespartnered with Lynda.com use the tutorials as added features to their existing courses.  When asked in an interview with ReadWriteBuilders, if high technical companies look at online programs in terms of advancement as a supplement to traditional education or as a way for people to further their careers, Lynda feels that “it’sjust one example of something that you can do to enhance your attractiveness to potential employers. But [it’s also important to have] a portfolio and body of work, references that actually work out, showing that you had success in the past.”

MOOC Benefits:

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.