IT Outsourcing came to foray as a means for corporations to focus on critical business operations while having a specialized IT company take over the responsibility of managing the IT infrastructure and application development. For corporations especially in the developed countries, IT outsourcing provided two fold advantages, one was access to a highly talented pool of engineers and that too at a lower cost since countries like India were quickly growing their stature as an IT outsourcing hub.

IT Outsourcing is now as mainstream as ever and almost every leading organization outsources some or all parts of its IT infrastructure to a specialized company. It makes pure business sense and with tightening budget controls, IT outsourcing has become one of the strategic cost reduction driver for most organizations. Moreover, IT outsourcing is no more restricted to companies in USA & Europe outsourcing their IT projects to countries like India. Domestic companies within India itself actively use IT outsourcing including the Indian government like the India Post project given to TCS.

Is it then a no brainer that IT Outsourcing is critical to your business? Well, if it is cheaper and does not seem to have any inherent disadvantages why not!! Not really, IT Outsourcing despite proven benefits has its limitations and you should be cognizant be of the same before considering outsourcing your IT operations.

·         Limitations in estimating the actual cost of IT outsourcing:Let’s tackle the biggest driver of IT Outsourcing-Cost Savings. For anyone to estimate the cost savings from IT Outsourcing one needs to be able to predict the cost of outsourcing which then helps understand the cost savings from the same. Yes, at a higher level it is a matter of a simple $ per man-hour costs and IT outsourcing will appear to be cheaper in almost all cases. However, “hidden costs” are commonplace with IT outsourcing and it can be immensely difficult to accurately predict these hidden costs. For example, you need to be able to identify the costs of transitioning your in-house IT to an outsourcer, management overhead needed to manage the outsourcing relationship etc. In addition, IT outsourcing contracts are fixed at the start of the contract and as a result any additional requirement/change tends to be charged additionally. It is no surprise that IT requirements can change frequently and if your outsourcing contract doesn’t account for flexibility, you might be limited in the actual cost savings you might make. There is no surprise that there have been so many instances of IT outsourcing projects overshooting their budgets by a huge margin such as the one government shared services project going 500 million pounds over budget

No matter what type of business you’re in, boosting your bottom line is always in the back of your mind. In a rough economy, it can be tempting to focus too much on pulling in more money and not enough on containing it from within.

That’s right, containing it. You have the potential to lose hundreds of thousands of dollars every year right under your nose from something as simple as lack of or ineffective computer training.

How much do the employees you have working for you right now really understand about technology? How good is your IT tech department? Technology changes faster than a blink of an eye and oftentimes, businesses struggle to keep their top employees trained.

With millions of dollars being lost to Internet espionage, file corruption and other computer crimes, staying on top of changes is essential. Recently, online learning centers have been emerging as the go-to method for quick and inexpensive learning. Unfortunately, this type of computer learning isn’t always the best solution.

Sage wisdom states that there are two sides to every coin. This timeless wisdom will be borne out in spades with Windows 8/RT. Let's get into the dark side first.

If your users are veterans of Windows it is safe bet they are going to take one look at Windows 8 and scream blasphemy. Users whose brains are geared towards visual learning will undoubtedly yell the loudest and longest.

There's a good reason for this. Mick Jagger brought his band to the Redmond campus, performing live "Start Me Up" in the summer of 1995 (it was a great show). This heralded in the abandonment of program icons sitting on the desktop and introduced the now legacy Start button.

Ending the life of the 17-year-old start button is not going to go well with some users.

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 */