There are normally two sides to the story when it comes to employment. On one hand, employers hold the view that the right candidate is a hard find; while on the other, job hunters think that it’s a tasking affair to land a decent job out there.

Regardless of which side of the divide you lay, landing good work or workers is a tedious endeavor. For those looking to hire, a single job opening could attract hundreds or thousands of applicants. Sifting through the lot in hope of finding the right fit is no doubt time consuming. Conversely, a job seeker may hold the opinion that he or she is submitting resumes into the big black hole of the Internet, never really anticipating a response, but nevertheless sending them out rather than sit back doing nothing.

A recruitment agency normally keeps an internal database of applicants and resumes for current and future opportunities. They first do a database search to try and identify qualified and screened candidates from their existing crop of talent. Most often the case, they’ll also post open positions online through industry websites and job boards so as to net other possible applicants.

When it comes to IT staffing needs, HR managers even find a more challenging process in their hands. This is because the IT department is one of the most sensitive in any given organization where a single slip-up could be disastrous for the company (think data security, think finances when the IT guys are working in tandem with accounts). You get the picture, right?

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

When businesses are trying to expand and require professionals to lead teams, terminology may get in the way of who performs what roles. When it comes to information technology (IT), new and vital professionals may seem hard to differentiate between one another. However, there are key differences between specific professionals needed with IT departments. Here are the responsibilities that differentiate between an IT manager and an IT project manager.

IT Managers

IT managers are the leaders of the entire IT infrastructure a business has to function properly. The IT manager must lead the entire IT department to regulate and maintain the IT network for the business. As a manager, this IT professional corresponds with other departments in the business about how the IT department is implementing the goals the business is aiming toward. In addition, the manager must be fiscally responsible and answer to executives and financial officers in the business the reasons behind certain costs and investments. Because of the dual computer technology and business acumen this profession requires, many IT managers have a Master of Business Administration (MBA) related to information technology.

IT Project Managers

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