IT/Software career thread: Invert binary trees for dollars.

Fucker

Log Wizard
17,285
42,942
In reality what will happen is this. Within the next 5 years or so people will be abstracted to only working with the agent window or similar and never seeing code of anything. This will be how they interact with it and while they will succeed at many things the knowledge of precisely how data loads into something, for example, will be lost to the greybeards who had to do it prior to AI.
This is going to be a prevalent problem across many industries as AI starts growing some teeth. It will build itself tools that no one knows how they operate, and it will build itself tools that they don't understand on any level. An early example of this as an AI tool was used to design a IC, and engineers said the outputs were completely unexpected and "alien".

In the TV show, Raised by Wolves, I wondered what could possibly create the Necromancer.

Now I know.

 

ShakyJake

<Donor>
8,829
21,619
In reality what will happen is this. Within the next 5 years or so people will be abstracted to only working with the agent window or similar and never seeing code of anything. This will be how they interact with it and while they will succeed at many things the knowledge of precisely how data loads into something, for example, will be lost to the greybeards who had to do it prior to AI.

Low level tasks are completely destroyed by AI and it creates the problem we have today. You do not get Senior engineers without hiring Junior engineers.

It will create a point of finality. If you get to a point where you cannot prompt your way out of a massive defect what do you do? AI is only as smart as your ability to tell it what to do. Especially where critical defects and bugs do not necessarily result in a programmatic error but the inability of the application to do what it is supposed to within the parameters required.

As a better example. At my previous job we had archaic data architecture from the 90s running critical aspects of the business. Over time this had been layered with more than 80 transformation steps built into MSSQL to meet growing business needs. This still worked, mostly, but its processing time was being dragged out by essentially O notation and complexity. You cannot turn this system off, it runs the business, and its scale is too large to replicate to build a corrected parallel solution. You have to fix it in place.

On top of that, none of the code running this is in one singular coherent repo or anything either. It's all old databases that predated source control.

How do you think AI could even diagnose that as it can't see all of it?
I mean, this sounds exactly like every other legacy system that already exists. We maintain an ancient ASP.NET WebForms app that started in the early .NET 2 days. Over the years people dumped in different third-party frameworks, flipped patterns every couple of years, and nobody ever cleaned the old stuff out. The result is spaghetti. A new developer ( junior or senior) looking at that mess for the first time is basically lost. Similar problem you described: jam packed repo, layers on layers, and we can't rewrite it because the business will balk at spending money fixing tech debt.

AI hitting a wall on a system it cannot fully see is not a new failure mode. Humans hit that wall every day on these things and we just live with it. The "you cannot prompt your way out of a massive defect" problem is just the same old "nobody on the team actually understands how this works anymore" problem with a different interface.
 

TJT

Mr. Poopybutthole
<Gold Donor>
47,802
131,796
Yes, the difference I see is that the way this is going the engineers in 10 years won't even be able to read code. Nor understand the basic elements of programming. Just "prompt made it work, prompt until it does what I want." But people are smart so what I see happening is not that an error is deduced to mean this issue must be in this location but that they will fit the AI into anything they need to diagnose then go from there.