The consulting industry is fiercely competitive and nets between $130B and $150B a year. In fact, professional consultants earn more money than many lawyers, doctors and other professionals. 

Offering free consultations is a common way for a software consultant to seize new accounts. But is there a red flag where a consultant may be giving away too many services for free? The worst scenario for a professional software consultant is to offer free services to the client and then never hear from them again once they no longer need their help. 

Although having the best intentions, many people will waste a consultant's time (i.e., client ignores or rejects any suggested approaches or solutions given by the consultant and seek the services of someone who will do it cheaper or will attempt to do it themselves). Small business owners especially can be challenging to work with. Some clients have a tendency to jump into projects before having adequate resources to finish what they have started, decide to go in a different direction midstream, while others simply don't want to spend any money when getting professional services. It's hard to believe, but some clients actually expect to receive free services for life. To counteract this notion, a software consultant can draw the line by offering free services within a promotional time frame and then begin charging a fee for services rendered after that time.

A good indicator of what a client's true intentions are is to monitor their activity within a specified period to see if their consultation activity bears fruit in the form of a contract. One big red flag is non-commitment on the part of the client. If they seem indecisive or vague about what they want it may be time to move on. Although there are times when a free consultation results in a paying client years later, who can wait that long? 

Less of Your Time is Wasted When You're Upfront

After being burned, some professional software consultants no longer give free consulting. They find that clients are much more willing to follow their advice when they have paid something. In order to close an account, a happy medium can be agreed upon by both parties involved as a way to build a long term relationship with highly qualified prospects. 

A software consultant's work, knowledge, skills and time are valuable. They can offer a potential client general solutions instead of addressing specific challenges. If a specific topic of discussion, troubleshooting session or other issue needs to be addressed, the consultant can inform the client of any upfront costs to receive a particular service if they need further assistance. Really, a free software consultation (if one is given) should be presented in a very similar way someone would hand out samples of a product at a grocery store. A professional consultant ideally wants clients to see how they can benefit using their services on a trial basis with a pitch leading to more extensive services which would only be available if they sign a contract with their firm. 

 Red Flags

I’ll get straight to the point.  Why should companies invest more in management training?  Here are 10 simple reasons.

1) An employee’s relationship with his or her direct manager is the most important single factor in employee engagement.

2) Engaged employees are happier and more productive.  Disengaged employees are frustrated and more disruptive.

3) Because there’s no widely agreed-on skillset for management (good managers come in all shapes and sizes), there’s an assumption everyone knows how to do it.  This is akin to someone who’s never driven before being given keys to a car and told: “Drive.”  (Many many years ago, this is how I first learned to manage.  I blundered my way through it.  Trial and error.  It wasn’t pretty.)

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

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?