I just figured out why software contracting and consulting are dead

[The Gorn]

I figured out one extremely simple reason why it is very difficult to maintain a software contracting worklife today. Well, it's not simple in its components, but it is one unifying principle that you see behind the collapse of computer consulting.

A consultant always has to stay at least one, and preferably two or three steps ahead of his clientele.

If you can't do this consistently, you can't consult.

For software development, this means knowing about platforms before they are in general use, and anticipating when they will take off, and leveraging that knowledge.

I look back to my best years of consulting and that was certainly true. I knew Windows development, none of my clients were good at it, so I was two steps ahead at least.

As that lead narrowed, so did my contracting options. Pretty much in a 1:1 pattern.

Today, maintaining this lead is just about impossible. For one thing, clients can turn on a dime and scrap one platform and embrace another in which you have no experience.

The best almost anyone can do is barely keep up with their current gig.

Therefore, no software consulting. We're all commodities owing to the churn of development tools and platforms.

Thoughts?

[TRexx]

I heartily agree.

Most high-end technical consultants spend a considerable amount of non-billable time maintaining their expertise. This means they attend conferences, seminars and pay for training.  You have to demand a very high rate in order to sustain that.

[DG9]

Ditto Gorn.  The field has widened and changes so fast it became impossible (for me) to stay/get current at any depth while guessing the right tool/platform/whatever of the day.   It was fun back in the day, but so were a lot of other things.  Times change...

[The Gorn]

I'm saying also that this transcends the issue of H1Bs. Programming has become a mass phenomenon.

And also - to be a consultant implies that you have deep, specific subject matter knowledge. With the rate of change of today's platforms, absolutely nobody meets that standard in most popular languages and tools.

[DG9]

Yep, being legitimate SME is key.

[Richardk]

I agree and with "programming" becoming more common, it's difficult to distinguish yourself from someone who just learned it 'last night'. Meaning that perhaps you don't need that 'deep' knowledge since many tools are powerful and easy to use. If you can impress the client then you're golden.

I'm also seeing more and more demand for specific tools, packages and certifications that add nothing to "programming" but suddenly you also need to be the "black belt" in inventory control, or just in time or compliance with some laws. Like really? Hire an attorney, don't ask me whether you're compliant while paying a 'starting salary'.

Lastly I'm seeing "consultants" that are really techies doing misc. work, like installing antivirus software, setting up a PC, simple networking and server setups, issues with Access or web browsers, etc. I feel that dilutes the title and if "the last 'consultant' who installed Norton, only charged $X then why do you want more?"

[benali72]

Good insight, Gorn. I agree.

I think the one viable area of consulting left is to pick the right area to be "the expert" in and then stick with it. For example, I know some DB2 consultants who have been at it for twenty years. But very, very few of us have both the skill -- and the luck -- to pick an area like this that stays viable for so long.

So like you said, consulting has taken a dive for most of us.

[Origisaurus]

. . . compliance with some laws. Like really? Hire an attorney, don't ask me whether you're compliant while paying a 'starting salary'.

Giving legal advice is the exclusive field of those $500/hour lawyers.  And of course a techie or anyone not licensed to practice law can get into deep doo-doo by doing so.  A "client" who wants the same advice from a $100-or-less/hour techie is in serious need of remedial education, if not already a basket case.

. . . if "the last 'consultant' who installed Norton, only charged $X then why do you want more?"

Anyone who needs or wants to quibble about rates may be in need of a consultant, but they want to hire a grunt.  If you feel like doing missionary work, bringing the gospel to the heathen, go for it, if not, disqualify them and ambulate.

[TRexx]

Another reason is that there isn't as much need for the pure technical consultant anymore. i used to earn a nice living just keeping operating systems alive and well.  But the quality of the software has improved (or after 40 years IBM has finally fixed all the bugs     ) so there just isn't as much to do.  Factor in all the consolidations and mergers and a shop that had maybe a dozen systems programmers now has  4 or 5. 

[Richardk]

A "client" who wants the same advice from a $100-or-less/hour techie is in serious need of remedial education, if not already a basket case.

Well, I'm seeing more of it and not just for consultants but for "jobs" as a FTE. "It's your job that we stay compliant with blah-blah-blah". It's one thing to implement a system but then it's just like any other spec, so why make such a big deal about it? On the other hand if you need to interpret the law and draw up guidelines, that's totally different.

Anyone who needs or wants to quibble about rates may be in need of a consultant, but they want to hire a grunt.  If you feel like doing missionary work, bringing the gospel to the heathen, go for it, if not, disqualify them and ambulate.

That's part of the problem. They look like a qualified client but there's something wrong. Sometimes it's clear when you first meet but very often you don't draw that conclusion until much further into the relationship or when it's time to pay the bill. And it might not be about the rate but rather the amount of work such as "oh, our estimate was 4 hours, not 4 days". Of course they don't tell you this upfront, even when you give them your estimate.

[Richardk]

Another reason is that there isn't as much need for the pure technical consultant anymore. ... Factor in all the consolidations and mergers and a shop that had maybe a dozen systems programmers now has  4 or 5.

I see a lot of this in the local job market. Many, many places don't need a pure technical person but rather a grunt that keeps the place running. And not a jack-of-all-trades type because that would be too expensive but basically the same job with a lower title and pay. And yes, places that consolidated only need a handful of pure tech staff.

I recall one place with an IT dept. of six people but none of them had a traditional job of being a programmer, analyst or DBA. One spent most of the day with company issued cell phones, another with laptops dealing with bad drives or something not working. The other with the network and setting up desktops, etc. One part time person was actually a programmer and the manager dabbled with the DB to get reports that management couldn't figure out how to run.

This didn't look like an IT Dept. to me and my only peer seemed to be the manager. Even then I think he was more into management than understanding all the technology. It just felt so wrong.

[choppedwood]

I'm also seeing more and more demand for specific tools, packages and certifications that add nothing to "programming" but suddenly you also need to be the "black belt" in inventory control, or just in time or compliance with some laws. Like really? Hire an attorney, don't ask me whether you're compliant while paying a 'starting salary'.

Where I really see this is in health care.  You almost have to have worked in it to work in it.

[choppedwood]

I recall one place with an IT dept. of six people but none of them had a traditional job of being a programmer, analyst or DBA. One spent most of the day with company issued cell phones, another with laptops dealing with bad drives or something not working. The other with the network and setting up desktops, etc. One part time person was actually a programmer and the manager dabbled with the DB to get reports that management couldn't figure out how to run.

This is, I think, more common than not.  You have businesses running around an ERP that handles almost all of the things they need.  In many cases those databases don't really need a full-time DBA and often you can't even write code for them because it's all locked down.  I know of a company, not sure how big but they have at least 10 locations, and it's run by one IT guy.  He sets up the phones, desktops and my best guess is that anything beyond that he calls up their ERP vendor.  20 years ago you'd have had 3 programmers, a network guy, a general support guy, and heck, some dude to even run and distribute paper-based reports.

[David Randolph]

The alternative is to provide software as a service. The real developers work for the service company and their development results are sold as a package.

So, don't be a "consultant", start your own company.

[unix]

then work for dot-gov.  Not only is it not affected by the H1 virus, they are 15 years behind the times. Had such a gig for a year now and am thoroughly enjoying it. The paychecks don't bounce and I want to learn absolutely nothing new anymore to be perfectly honest. But don't quote me on this.