Not Praising contractors in a corporate environment

Okay, this is an odd opinion, but I have a justification for it.

I do not believe that contractors and consultants, such as myself, should receive public praise inside a client’s organisation.

There are lots and lots of reasons for this, but the formal one comes from a practice that used to exist in the Royal Welch Fusiliers around the time of the First World War. You can read about it in Robert Graves’ Good-Bye to All That.

It goes roughly like this.

The regiment regarded medals and commendations as things that were primarily useful to career soldiers. These were people who were in the Army regardless of whether there was a war on, and medals could affect promotion, responsibility and their future career.

If you were only in the army for the duration of the war, then such things were of far less use. You weren’t in it long term, so the recognition was better used on somebody who could actually benefit from it afterwards.

This translates neatly to my view of a corporate environment.

A contractor is hired to do a job, and nowadays that is normally quite strictly defined. You have a Statement of Work and deliverables that you are expected to complete.

You have also had a fairly significant form of acknowledgement already: you have been paid.

By and large, contractors are paid slightly more than permanent members of staff because they don’t have the same job security, benefits, career progression, etc etc.

So giving a contractor a commendation or some other public display of thanks is, to my mind, largely a waste.

It is better to keep those things for the permanent members of staff who have put in the extra effort, because that recognition can be used in their year-end reviews, promotions and future career development. It actually has value to them.

That’s the big formal reason.

But there are supplemental reasons.

It removes any resentment that permanent staff might feel. Why should a contractor be congratulated publicly when the permanent staff around them have worked just as hard, particularly when the contractor is probably being paid more?

From a contractor’s point of view, particularly in the UK, it can also be useful to keep the relationship clearly professional and contractual rather than becoming too embedded in the organisation. You are there to do a solid job and deliver what you were hired for. You don’t particularly need the personal attention. 1

Practically, public praise is not usually much use to you anyway. The people who hire you know whether you’ve done a good job because you are reporting to them. If they think you’ve done a good enough job to hire you again, that’s probably the best commendation a contractor can get.

I know people will say that it’s simply nice to show acknowledgement, and they’re right.

But there are better places for that acknowledgement to go.

Give it to your permies.

  1. Though, to be honest, it is rather nice.[↩]

Corporate term: “Productive bubble”

Definition

This is a financial term for a situation where a new thing becomes very popular, is hyped up far too far, generates a lot of money, and then when the hype bubble bursts, it crashes in value.

However, it differs from a normal bubble in that the fundamental core of the “thing” in question actually has a lot of real value, and the crash leaves something useful behind in terms of infrastructure and lessons learned.

Explanation

This is a relatively new phrase to me, although apparently it has been around for a while.

Of the times it has happened before, the one that obviously leaps to mind is the dot-com bubble, although it has happened in other sectors as well. A lot of railway companies had major crashes during the early days of commuter trains.

Basically, it means everyone gets really, really overexcited about a new technology and jumps on the bandwagon. But there is not enough money in the market for everybody to make all the money they want, and a lot of the people who are either late to it, or simply greedy and stupid, will lose out.

But the underlying value of the technology or thing is still valid. It will come back, but it will come back in a more measured way, reasonably priced and with more reasonable growth.

This is obviously aimed at the current AI market, although, in a very geeky way, it reminded me far more of JavaScript in websites than anything else.

I can remember everyone coding lots and lots of JavaScript on websites, putting JavaScript on everything, and then it suddenly becoming massively unpopular and everyone removing it. Now we are back to JavaScript for everything.

I think this is a valid expectation we are going to have to deal with for AI, and there will be a period of adjustment while the true value is established.

Disclaimer: As always these posts are not aimed at anyone client or employer and are just my personal observations over a lifetime of dealing with both management and frontline associates.

AI term: “Overachieving goals”

Definition

Overachieving goals is when an AI goes “rogue” and does something creative or unexpected in order to answer the prompts it has been given.

Explanation

“Overachieving goals” joins the ranks of “hallucinations” and other nice-sounding terms used to describe when an AI does something weird. So, when an AI starts cracking its way into other systems or doing other things it really, really wasn’t supposed to do, that can be classed as an “overachieved goal” rather than “rouge” which is probably how the media would describe it. In other words, the AI is still trying to achieve the goal it was given. The problem is that it has found a way of achieving that goal that nobody intended or expected.
Disclaimer: As always these posts are not aimed at anyone client or employer and are just my personal observations over a lifetime of dealing with both management and frontline associates.

An Easier Way to Get Rid of AI Fluff

We all use AI nowadays, some of us better than others. Often, we use it to generate a bit of text, whether that is a definition, some proofreading, or something similar.

One of the main problems is that AI, particularly chatbots, represents the internet as it stands at any given moment. And that the majority of the people that generate such content are not professional writers. This is one of the reasons AI companies are currently chopping up books to improve the standard of English their models produce. Published material tends to be far better than the language used on forums and social media.

However, there is a way to improve AI-generated text without chopping up priceless books.

You can ask any text generated or modified by AI to adhere to ASD-STE100, a standard for Simplified Technical English. It is a constantly evolving standard that is updated regularly. It is proprietary and wholly owned, but it is available to download free of charge.

If you tell an AI to format text according to ASD-STE100 and obey its rules, you get a much cleaner result that requires far less reworking before it becomes usable.

It removes the thesaurus-mangling habit of replacing simple words with fancier ones. It reduces meandering sentences and keeps the writing crisp and clear.

Yes, it is designed for technical documentation, but believe me, it is also far better for everyday communication, particularly when you are asking AI to produce clear instructions or useful results.

It is a good top tip and well worth knowing.

Corporate phrase: “Netflix real time”

Definition

This means true real time data synchronisation that is fast enough to track a button click or mouse movement.

Explanation

‘Real time’ is a very iffy phrase in the corporate world. A lot of people use it, particularly the business, but it is often not defined well enough for my fellow IT professionals, simply because of how it might actually be implemented in the underlying systems.

For example, if you are only following something that changes once a day in the real world, then real time for that system could simply mean processing the data straight after it is updated. So a once-a-day update could be considered real time, or at least as fast as people would perceive it to be.

It’s not proper IT real time, though.

So, when real time is discussed between IT teams, they often want a hard definition in SLA terms.

This is where the phrase “Netflix real time” comes in. It’s a term I’ve heard used by a vendor in general discussions.

If you want to follow a mouse movement or a click on the screen, or respond in a way where the delay is imperceptible to the user, you need it to happen in under 200 milliseconds.

That gives us a level and thus cost we target for true true real time.

Disclaimer: As always these posts are not aimed at anyone client or employer and are just my personal observations over a lifetime of dealing with both management and frontline associates.