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?

Outsourcing IT needs in the corporate world has become extremely popular because it is cost-efficient and it gives IT resources to companies that may not otherwise be able to afford them. Another positive side effect of IT outsourcing is that it has brought many technology jobs back to the United States.

As convenient and patriotic as IT outsourcing has become, it also have several limitations that have caused many companies to re-think the idea of funding their own internal IT group. It is important for a company to be completely familiar with these limitations before developing any kind of company policy in regards to IT.

The Customer Could Outgrow The Outsource Company

When an IT outsourcing company first takes on a new client, the relationship is beneficial to both sides. But things can start to get inconvenient for the client when the client's business starts to outgrow the capabilities of the IT outsource group.

An IT outsourcing company can become entrenched in the daily routine of its clients, which is great at first. But when the IT company can no longer keep pace with the growth of its clients, then the clients are stuck trying to find a new solution and keep track of its own IT assets at the same time.

The IT Outsourcing Company Lacks The Necessary Technical Expertise

IT outsourcing clients like to believe that their support company knows everything there is to know about computers and the Internet. But every IT support company has its areas of expertise and they have the technical areas where they are not quite as strong. If the client starts to experience needs from the areas where the IT outsourcing company is not so strong, then that can become a significant business issue.

This problem can be amplified if the client is a small business experiencing growth. An IT outsourcing company is not as likely to bring on new personnel for a smaller client, which leaves the client without a solution.

The Client Losses A Measure Of Control Over Its Data

No matter how large or successful an IT outsourcing company may be, there will always be the limitation of client security and the protection of critical customer data. All it takes is one rogue employee of the IT outsourcing company to compromise all of the client's critical data.

Some IT outsourcing companies have safeguards put in place to try and prevent client data compromise, but those safeguards are limited by how much access the IT company has to the client network. In most cases, that access has to be comprehensive for the IT outsourcing company to be able to do its job.

Outsourcing IT responsibilities can take a lot of stress off of a client and allow that client to operate his business by focusing on his core competencies. But there are limitations to IT outsourcing that could make it necessary for a client to do his own IT support and pay the extra costs.

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

Applications are becoming more and more sophisticated as languages such as Python open the doors to the world of programming for people who have the creative vision but always felt actually writing code was beyond their grasp.

A large part of any programs success is based on how well it can react to the events which it has been programmed to understand and listen for.

A good example of an event would be when the user clicks a button on the applications window. What happens when that button is clicked?

Well, the first thing that happens is the operating system sends out a message to let any listening software know that the button was clicked. Next, your application needs to do something in response to that event.