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

F# is excellent for specialties such as scientific computing and data analysis. It is an excellent choice for enterprise development as well. There are a few great reasons why you should consider using F# for your next project.

Concise

F# is not cluttered up with coding noise;  no pesky semicolons, curly brackets, and so on. You almost never have to specify the kind of object you're referencing because of its powerful type inference system. It usually takes fewer lines of code to solve the same issue.

Convenient

Common programming tasks are much easier in F#. These include generating and using state machines, comparison and equality, list processing, as well as complex type definitions. It is very easy to generate powerful and reusable code because functions are first class objects. This is done by creating functions that have other functions as parameters or that combine existing functions to generate a new functionality.

Correctness

F# has a strong type system, and, therefore, prevents many common errors such as null reference exceptions. Valuables are immutable by default which, too, prevents a huge class of errors. You can also encode business logic by utilizing the type system. When done correctly, it is impossible to mix up units of measure or to write incorrect code thereby decresing the need of unit tests.

Concurrency

F# has number of built-in libraries. These libraries help when more than one thing at a time is occurring. Parallelism and asynchronous programming are very simple. There is also a built-in actor model as well as excellent support for event handling and functional reactive programming. Sharing state and avoiding locks are much easier because data structures are immutable by default.

Completeness

F# also supports other styles that are not 100 percent pure. This makes it easier to interact with the non-pure world of databases, websites, other applications, and so on. It is actually designed as a hybrid functional/OO language. F# is also part of the .NET ecosystem. This gives you seamless access to all the third party .NET tools and libraries. It operates on most platforms. These platforms include Linux and smartphones via mono. Visual Studio is integrates with F# as well. This means you get many plug-ins for unit tests, a debugger, a IDE with IntelliSense support, other development tasks. You can use MonoDevelop IDE on Linux.

Related:

F# - Marching Towards Top 10 Programming Languages

What Are the Advantages of Python Over Ruby?

Top 10 Programming Languages Expected To Be In Demand in 2014

It’s the eternal conundrum of a hiring manager – you have to hire for every single position in the company without any first-hand experience. How to do it? If you can have a trusted programmer sit in on the interview, that’s ideal, of course. But what if you’re hiring your first programmer? Or what if you’re hiring a freelancer? Or what if company policy dictates that you’re the only person allowed to do the interviewing? Well, in that case, you need some helpful advice and your innate bullshit detector. We questioned programmers and hiring managers and compiled a list of dos and don’ts. Here are some things to ask when interviewing programmers:

Past Experience

Ask the programmer about the biggest disaster of his career so far, and how he handled it. Did he come in at midnight to fix the code? Was he unaware of the problem until someone brought it up? Did someone else handle it?  According to our programmer sources, “Anyone worth their salt has caused a major meltdown. If they say they haven’t, they’re lying. Or very, very green.” Pushing a code with bugs in it isn’t necessarily bad. Not handling it well is bad.

As usual, your biggest asset is not knowing the field, it is knowing people. Asking about career disasters can be uncomfortable, but if the interviewee is experienced and honest then she won’t have a problem telling you about it, and you will get an idea of how she handles mishaps. Even if you don’t understand what the disaster was or how it was fixed, you should be able to tell how honest she’s being and how she handles being put on the spot.

From Brennan's Blog which is no longer up and running: