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

With the rise of the smart phone, many people who have long seen themselves as non-gamers have began to download and play to occupy themselves throughout the day. If you're a game developer who has a history of writing your code in C#, then perhaps this still emerging market is something you should consider taking advantage of. This, however, will require the familiarization with other programming languages.

One option for moving away from the C# language is to learn Java. Java is the programming used for apps on the android platform, billions of phones run on this programming language.

If you want to break into the android market, then learning Java is an absolute must.

There are both some pros and some cons to learning java. Firstly, if you already know C# or other languages and understand how they work, then java will be relatively easy to learn due to having similar, but quite simplified, syntax to C-based languages, the class library is large and standardized, but also very well written, and you might find that it will improve the performance and portability of your creations. Not to mention, learning java opens you up to the entirety of the android app and game market, a very large and still growing market that would otherwise stay closed off to you. That's too much ad and sale money to risk missing out on.

The few cons that come with learning the language is that, when coming from other languages, the syntax may take some getting used to. This is true for most languages. The other problem is that you must be careful with the specifics of how you write your code. While java can be written in a very streamlined fashion, it's also possible to write working, but bulky, code that will slow down your programs. Practice makes perfect, and the knowledge to avoid such pitfalls within the language.

If you wish to develop for the iOS on the other hand, knowledge of Objective C is required. The most compelling reason to learn Objective C is the market that it will open you up to. According to the website AndroidAuthority.com, in the article "Google play vs. Apple app store", users of iPhones and other iOS devices are much more likely to spend money on apps rather than downloading free ones.

Though learning Objective C might be a far jump from someone who currently writes in C#, it's certainly learn-able with a little bit of practice.

How do top programmers work?

What are a few unique pieces of career advice that nobody ever mentions?

Good non-programmer jobs for people with software developer experience

A string in Python is enclosed in either single or double quotes.  Therefore, either one does the trick.  A common practice is to place single words with no characters that can be interpolated in single quotes and multi-word strings that contain interpolated characters in double quotes.  This may be a carry over from Perl where interpolated characters are in double quotes. 

If you do not want to interpolate a string, use a raw string ... r"\n".  With the exception of the last print statement, each of the print statements prints hello on a separate line from how are you?.  They are great for regular expressions.

Finally, triple double quotes """ some message about a function or class ... """ are used for docstrings.

print "hello \n how are you?"
print 'hello \n how are you?'
print r"hello \n how are you?"