I’ve long been interested in technology and its potential to make life easier and more efficient. However, I’m definitely not a pointy-headed tech nerd. Tech jargon user-unfriendly pieces of software drive me insane.
One of my particular pet peeves is the ability of the tech world to make something simple and every day sound much more complicated than it actually is.
One of my favourite toe-curlers is ‘boot up’ or ‘reboot’. For the ordinary folk in the room, ‘start’, ‘switch on’ or ‘restart’ seems like a perfectly reasonable and well-understood alternative.
And it’s amazing how, just when you thought you had heard all the weird and wonderful terms that the tech world can come up with, you discover a new one.
I honestly don’t know if this has come into use recently with the arrival of AI or if it has been around for a while and I’d just never come across it before; but a newly discovered tech term for me is ‘ingest’ or ‘ingestion’.
Now the standard usage, of course, would be in a biological or medical context.
But in the best traditions of tech jargon, this slightly obscure verb/noun combination, which is definitely not used much in everyday speech, has become the standard way to describe how a file or doc has been uploaded and chunked by a GPT’s knowledge base.
Granted, it is a term that most people will more or less understand; and, ‘yes’ there is some logic behind its use. In a biological/medical context, of course, it describes the full consumption/digestion of something into something else; and this is clearly the intent behind the tech usage.
But really? Couldn’t we just say, the files have been uploaded and chunked?
Of course, the annoying thing about all of this jargon is that once it’s established, if you are working in a tech context in which it is used, at the very least you have to make the effort to understand it; and (shudder) eventually you’ll almost certainly find yourself using it.
In short, sometimes you have no choice but to learn to speak the tech ‘lingo.’
If you have read some of my recent posts, you’ll know that I’m in the early stages of building an AI-powered app for L&D called PerformaGo. I’m also keeping a diary-like blog which is documenting the journey ‘behind the scenes.’
I’ve divided the diary into 4 broad sections, one of which is called, ‘Learning to speak API’. It’s all about understanding, unpacking and explaining the tech ‘lingo’ and concepts so they make sense to me and to ordinary readers like you.
So, why not follow along if you are interested. And if you’ve got any particular tech-speak pet-peeves, I’d love to hear from you.