INSIGHTS

There will be life after AI? Yes — but it will be more expensive. How to mitigate it? Let’s talk.

For some time, we said AI would change technology. Later, we said it would change business. And finally, that AI would change the world. Setting aside the hype, which tends to make everything seem overestimated, AI will indeed change practically everything. I remember a long time ago a professor — a very bad one, by the way — talking about pervasive computing as something that would invade our cities and change the world. I remember being shocked, and in fact pervasive interaction did emerge and is now a reality. But one fundamental point kept adoption modest compared to what was predicted: costs.

The question I ask now is: Who is looking at the costs of AI? Especially those hidden costs — the ones that usually break companies and inhibit technologies. A few days ago, I read an inspiring post by the great José António Carpio reflecting on some claims about time savings in development. That sparked an insight that has been blowing my mind: the hidden costs of AI.

One of the points that has become increasingly clear to me is that investments in quality and security associated with Artificial Intelligence are not keeping up with investments in development. This is already a problem, but it will soon become a monster. I keep saying that AI in testing is just as important — or even more important — than AI for testing.

The narrative that AI will save the world and change the world is true, and those who are not studying and updating themselves will be left behind. It won’t be over-engineering or over-programming that saves you, but rather a critical and holistic view of what is being done. AI is a tool — perhaps the most remarkable tool humanity has ever created — but a hammer won’t save you when what you need is to tighten a screw. Knowing how to use the tool is just as important as having it.

Those who ignore the costs are walking straight toward failure, and one thing the hype has done is generate excitement that prevents people from noticing the hidden costs. But now, who will defend us? I would recommend, for now, a review of the quality and security issues you are adding to your code. I wouldn’t leave aside, however, the costs of supervision and training. Do you agree? Let’s talk!

Jose Antonio Carpio original linkedin Post: https://www.linkedin.com/posts/joseantoniocarpio_ia-productividad-automatizaciaejn-activity-7432742513880330240-dQnk?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAOgxk0BEHdKWSpzkI4TnZE_XlG5iAma0f4

Enjoy this insight? Share it!

Learn more

Let’s talk