Like me, I believe most people go about their business never to give a serious thought about their assumed private correspondence when using Gmail to email friends, colleagues and business associates.  As it turns out, your daily banter may not be so private after all.  A recent article in Fortune Magazine, “Judge Rejects Google Deal Over Email Scanning” caught my attention and an immediate thought dominated my curiosity…Google email and scanning scam.  

In essence, the article describes Googles’ agreement to change the way it scans incoming messages so that it no longer reads emails while they are in transit, but only when they are in someone's inbox! So, what exactly does that mean? Judge Koh, a San Francisco federal judge, said she's not so sure about that. Her ruling claims the settlement does not provide an adequate technical explanation of Google's workaround, which involves scanning in-transit emails for security purposes, and then later parsing them for advertising data. The judge also proposed a legal settlement to pay $2.2 million to lawyers, but nothing to consumers.

My interest in this story is not so much about the proposed settlements or the specific details about how Google or any of the web giants settle claims based on vague legal language. It is however, more about the naiveté of myself and perhaps many others that never question how the email scanning process really works. I wonder, do most of us really care that Gmail uses contents of our mail to display targeted ads?

Big data is now in an incredibly important part of how many major businesses function. Data analysis, or the finding of facts from large volumes of data, helps businesses make many of their important decisions. Companies that conduct business on a national or international scale rely on big data in order to plot the general direction of their business. The concept of big data can be very confusing due to the sheer scale of information involved.  By following a few simple guidelines, even the layman can understand big data and its impacts on everyday life.

What Exactly is Big Data?

Just about everyone can understand the concept of data. Data is information, and information is everywhere in the modern world. Anytime you use any piece of technology you are making use of data. Anytime you read a book, skim the newspaper or listen to music you are also making use of data. Your brain interprets and organizes data constantly from your senses and your thoughts.

Big data, much like its name infers, simply describes this same data on a large sale. The internet allowed the streaming, sharing and collecting of data on a scale never before imaginable and storage technology has allowed ever increasing hoards of data to be accumulated. In order for something to be considered “big data” it must be at least 10 terabytes or more of information. To put that in perspective, consider that 10 terabytes represents the entire printed collection of material in the Library of Congress. What’s even more remarkable is that many businesses work with far more than the minimum 10 terabytes of data. UPS stores over 16 petabytes of data about its packages and customers. That’s 16,000 terabytes or the equivalent to 1,600 printed libraries of congress. The sheer amount of that data is nearly impossible for a human to comprehend, and analysis of this data is only possible with computers.

How do Big Data Companies Emerge?

All of this information comes from everywhere on the internet. The majority of the useful data includes customer information, search engine logs, and entries on social media networks to name a few. This data is constantly generated by the internet at insane rates. Specified computers and software programs are created and operated by big data companies that collect and sort this information. These programs and hardware are so sophisticated and so specialized that entire companies can be dedicated to analyzing this data and then selling it to other companies. The raw data is distilled down into manageable reports that company executives can make use of when handling business decisions.

The Top Five:

These are the five biggest companies, according to Forbes, in the business of selling either raw data reports or analytics programs that help companies to compile their own reports.

1. Splunk
Splunk is currently valued at $186 million.  It is essentially a program service that allows companies to turn their own raw data collections into usable information.

2. Opera Solutions
Opera Solutions is valued at $118 million. It serves as a data science service that helps other companies to manage the raw data that pertains to them. They can offer either direct consultation or cloud-based service.

3. Mu Sigma
Mu Sigma is valued at $114 million.  It is a slightly smaller version of Opera Solutions, offering essentially the same types of services.

4. Palantir
Palantir is valued at $78 million.  It offers data analysis software to companies so they can manage their own raw data analysis.

5. Cloudera
Cloudera is valued at $61 million.  It offers services, software and training specifically related to the Apahce Hadoop-based programs.

The software and services provided by these companies impact nearly all major businesses, industries and products. They impact what business offer, where they offer them and how they advertise them to consumers. Every advertisement, new store opening or creation of a new product is at least somewhat related to big data analysis. It is the directional force of modern business.

Sources:
http://www.sas.com/en_us/insights/big-data/what-is-big-data.html

http://www.forbes.com/sites/gilpress/2013/02/22/top-ten-big-data-pure-plays/

http://www.whatsabyte.com/

Related:

How does Google use Python?

Top Innovative Open Source Projects Making Waves in The Technology World

Is the U.S. the Leading Software Development Country?

How to Keep On Top Of the Latest Trends in Information Technology

In programming, memory leaks are a common issue, and it occurs when a computer uses memory but does not give it back to the operating system. Experienced programmers have the ability to diagnose a leak based on the symptoms. Some believe every undesired increase in memory usage is a memory leak, but this is not an accurate representation of a leak. Certain leaks only run for a short time and are virtually undetectable.

Memory Leak Consequences

Applications that suffer severe memory leaks will eventually exceed the memory resulting in a severe slowdown or a termination of the application.

How to Protect Code from Memory Leaks?

Preventing memory leaks in the first place is more convenient than trying to locate the leak later. To do this, you can use defensive programming techniques such as smart pointers for C++.  A smart pointer is safer than a raw pointer because it provides augmented behavior that raw pointers do not have. This includes garbage collection and checking for nulls.

If you are going to use a raw pointer, avoid operations that are dangerous for specific contexts. This means pointer arithmetic and pointer copying. Smart pointers use a reference count for the object being referred to. Once the reference count reaches zero, the excess goes into garbage collection. The most commonly used smart pointer is shared_ptr from the TR1 extensions of the C++ standard library.

Static Analysis

The second approach to memory leaks is referred to as static analysis and attempts to detect errors in your source-code. CodeSonar is one of the effective tools for detection. It provides checkers for the Power of Ten coding rules, and it is especially competent at procedural analysis. However, some might find it lagging for bigger code bases.

How to Handle a Memory Leak

For some memory leaks, the only solution is to read through the code to find and correct the error. Another one of the common approaches to C++ is to use RAII, which an acronym for Resource Acquisition Is Initialization. This approach means associating scoped objects using the acquired resources, which automatically releases the resources when the objects are no longer within scope. RAII has the advantage of knowing when objects exist and when they do not. This gives it a distinct advantage over garbage collection. Regardless, RAII is not always recommended because some situations require ordinary pointers to manage raw memory and increase performance. Use it with caution.

The Most Serious Leaks

Urgency of a leak depends on the situation, and where the leak has occurred in the operating system. Additionally, it becomes more urgent if the leak occurs where the memory is limited such as in embedded systems and portable devices.

To protect code from memory leaks, people have to stay vigilant and avoid codes that could result in a leak. Memory leaks continue until someone turns the system off, which makes the memory available again, but the slow process of a leak can eventually prejudice a machine that normally runs correctly.

Related:

The Five Principles of Performance

In Demand IT Skills

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.