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

Below are two pdf's which discuss and outline the Java Message Service, JMS, tutorial.

One Hour Java Messaging Service Tutorial
Advanced One Hour Java Messaging Service Tutorial

 

F#, which is usually pronounced as F sharp is one of the newly launched and rapidly developing programming languages.  It has recently become focus of attention due to its quick advancement to the 12^th position in the recent TIOBE index and the overall rise in popularity.

What is F#?

F# is an open source, functional and object oriented programming language which is available in cross platform. It was developed by a company called F# software foundation with help of Microsoft and other open contributors. F# runs on Linux, windows, iOS, Android and the GPUs and HTML as well. It is a mature programming language which helps the users as well as the organizations to solve the complex problems in a much simpler way with easy code. With its wide range of usage in the specialist and application areas, it is proving itself to be a worthy contender for the top 10 list.

Why choose F#?

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