Recently, the new iOS update had added Reminders to the iPhone. If you ever found yourself setting notes on your iPhone to remember to do things, such as buying milk while at the grocery store, this process has become leagues upon leagues simpler, and faster. On your iPhone is an application named “Reminders”. Tap on this application and experience the new world of To-Do lists.

Right away, you are greeted by a screen that looks similar to a notepad, where you would be scribbling down reminders for this, and for that. To start off, tap on the plus button, and you are able to input the reminder you want. Say you want to be reminded to “Buy Milk.” Just type that into the application and you’re good to go.

But wait, there’s more. What this new application brings to the table that is extremely useful is the fact that your iPhone can remind you to do that task at a certain location, which, in this case, is buying milk. If you had saved your regular grocery store in your Maps application as a favorite location, you are able to do so. (To save a favorite location, go into your Maps application, search for your nearest grocery store that you regularly shop at, tap on the pin, tap on the blue arrow to get more information, and “Add to Bookmarks.”) In order to remind you to buy milk at your favorite grocery store, slide the “Off” to “On” and you are now able to set where you would like to be reminded at, and at what point in time. Now, you will never leave the grocery store without buying milk!

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

I suspect that many of you are familiar with the term "hard coding a value" whereby the age of an individual or their location is written into the condition (or action) of a business rule (in this case) as shown below:

if customer.age > 21 and customer.city == 'denver'

then ...

Such coding practices are perfectly expectable provided that the conditional values, age and city, never change. They become entirely unacceptable if a need for different values could be anticipated. A classic example of where this practice occurred that caused considerable heartache in the IT industry was the Y2K issue where dates were updated using only the last 2 digits of a four digit number because the first 2 digits were hard-coded to 19 i.e. 1998, 1999. All was well provided that the date did not advance to a time beyond the 1900’s since no one could be certain of what would happen when the millennia arrived (2000). A considerably amount of work (albeit boring) and money, approximately $200 billion, went into revising systems by way of software rewrites and computer chip replacements in order to thwart any detrimental outcomes. It is obvious how a simple change or an assumption can have sweeping consequences.

You may wonder what Y2K has to do with Business Rule Management Systems (BRMS). Well, what if we considered rules themselves to be hard-coded. If we were to write 100s of rules in Java, .NET or whatever language that only worked for a given scenario or assumption, would that not constitute hard-coded logic? By hard-coded, we obviously mean compiled. For example, if a credit card company has a variety of bonus campaigns, each with their own unique list of rules that may change within a week’s time, what would be the most effective way of writing software to deal with these responsibilities?

IT jobs are without a doubt some of the highest paying jobs with information architects, data-security analysts and UX designers taking home $100,000 or more a year. But then again, these are high demand; high expertise jobs so don’t jump with joy as yet. But like every job and IT industry to be specific, not everyone commands such higher salaries. There are a large number of IT professionals who at some point of their career feel that their salaries have hit a standstill. Even if you are an IT professional and a great one at that, your technical expertise alone may not help you exceed the IT earning barrier. To continuously exceed your salaries, you need to work hard and smart. Here is how you can exceed the earning barrier in IT.

·         Gain Business Knowledge and Move Up The Management Ladder: IT departments for the most part are considered a part of “back office” operations. What this means is that despite being a core part of the business, IT professionals do not often get enough say in revenue generating components of the business and as a result seldom have a chance to take up senior management roles.  So if you do not want to stay content with a project manager or senior project management salary, invest time and money in gaining business knowledge. It could be through a formal business degree, online training courses or just by keeping your eyes and ears open while in the organization. Having the technical experience with business knowledge will instantly make you stand apart and open the doors for you to draw senior management salaries. For example, a survey conducted highlighted that CIOs were the biggest salary winners which clearly demonstrates the value of technical and business knowledge

·         Gain expertise on the “Hot” Technologies and Keep Learning: Say you are an expert in Java and draw a respectable salary in the industry. However, someone with less years of experience than you joins the organization and draws a higher salary than you! Why you ask. It could very well be because he/she is an expert in say big data technology such as Hadoop. Information Technology is one of the most dynamic industries with new technologies and languages coming up every now and then. When a new technology comes to the foray and gains traction, there is an instant demand-supply gap created which means that those with the specific skill sets are in a position to demand high salaries. If you have to break the IT earning barrier, always be ready to reinvent yourself by learning new technologies and this way you will be well positioned to jump on the high paying opportunities in the IT industry

·         Work On Your Own Side Projects: This one might seem controversial but let me clarify that I do not mean doing freelance work because even though your organization may never find out, it is ethically in breach of contract with your contract. If you have been lucky enough to be trained in some web based technologies such as Java, .NET or even HTML etc. spare sometime after office to build your own side projects. They could be very small projects tackling some problem that only you might have but there are multiple benefits of developing side projects. Worst case scenario, you will improve your technical skills. On the up side, you might end up creating your own business. A lot of technology start-ups were actually side projects the founders tinkered on with while they were employed full-time. You may not always succeed but there is no downside to the same