Data has always been important to business. While it wasn't long ago that businesses kept minimal information on people who bought their products, nowadays companies keep vast amounts of data. In the late 20th century, marketers began to take demographics seriously. It was hard to keep track of so much information without the help of computers.

Only large companies in the '60s and '70s could afford the research necessary to deliver real marketing insight. The marketers of yesteryear relied upon focus groups and expensive experiments to gauge consumer behavior in a controlled environment. Today even the smallest of companies can have access to a rich array of real-world data about their consumers' behavior and their consumers. The amount of data that is stored today dwarfs the data of only a few years ago by several orders of magnitude.

So what kind of information are businesses storing for marketing purposes? Some examples include:

- Demographic information — age, gender, ethnicity, education, occupation and various other individual characteristics.

Checking to see if a directory exists and then creating it if it is not present requires a few lines of code.  Isn't Python great.   Begin by importing the os module and use the exists and makedirs functions.

import os

if os.path.exists(somedirectory):
   os.makedirs(somedirectory)

What are some of the software development headaches associated with iPhone vs Android development?

The Boss (hereafter referred to as TB), handed me this research assignment. Hey, I finally got a little bit of one ups man ship on TB.

This is a significant moment in my life. Like me, TB isn't really human. I know because neither of us seem to indulge in that luxury known as sleep. That makes it extremely difficult to have any sort of 'gotcha'. I'm dancing. I got one.

In the warp speed development cycles we are now facing, TB must have gone to sleep, which in human terms is known as a wink. (About a 40th of the second).
18 June 2012 Monday, 3:30 PM (15:30 HRS) UTC -8, in Los Angeles Microsoft is making a major tablet announcement, revealing its own hardware that is tablet-based. Do not be surprised if it entails a Hollywood Inc. focus.

I will begin our blog on Java Tutorial with an incredibly important aspect of java development:  memory management.  The importance of this topic should not be minimized as an application's performance and footprint size are at stake.

From the outset, the Java Virtual Machine (JVM) manages memory via a mechanism known as Garbage Collection (GC).  The Garbage collector

• Manages the heap memory.   All obects are stored on the heap; therefore, all objects are managed.  The keyword, new, allocates the requisite memory to instantiate an object and places the newly allocated memory on the heap.  This object is marked as live until it is no longer being reference.
• Deallocates or reclaims those objects that are no longer being referened. 
• Traditionally, employs a Mark and Sweep algorithm.  In the mark phase, the collector identifies which objects are still alive.  The sweep phase identifies objects that are no longer alive.
• Deallocates the memory of objects that are not marked as live.
• Is automatically run by the JVM and not explicitely called by the Java developer.  Unlike languages such as C++, the Java developer has no explict control over memory management.
• Does not manage the stack.  Local primitive types and local object references are not managed by the GC.

So if the Java developer has no control over memory management, why even worry about the GC?  It turns out that memory management is an integral part of an application's performance, all things being equal.  The more memory that is required for the application to run, the greater the likelihood that computational efficiency suffers. To that end, the developer has to take into account the amount of memory being allocated when writing code.  This translates into the amount of heap memory being consumed.

Memory is split into two types:  stack and heap.  Stack memory is memory set aside for a thread of execution e.g. a function.  When a function is called, a block of memory is reserved for those variables local to the function, provided that they are either a type of Java primitive or an object reference.  Upon runtime completion of the function call, the reserved memory block is now available for the next thread of execution.  Heap memory, on the otherhand, is dynamically allocated.  That is, there is no set pattern for allocating or deallocating this memory.  Therefore, keeping track or managing this type of memory is a complicated process. In Java, such memory is allocated when instantiating an object:

String s = new String();  // new operator being employed
String m = "A String";    /* object instantiated by the JVM and then being set to a value.  The JVM
calls the new operator */