Cool, well I'm sure you'll get a lot of satisfaction from telling a machine to do your job for you.

You not only have to test to check that the things you asked for work as expected, but that there is no hidden functionality that you didn't ask for!

In a world with trained, experienced architects/designers/developers, you don't need AI. So the only reason to use AI is if you want to reduce your dependency on those expensive resources. But without that experience, the types of bugs that AI may generate are limitless.

This is a little different. Our entire world now relies on software.

While I'm I designing a process, I have the entire thing in my head and constantly run through all the logical possibilities. At the end of it, the types of bugs that are even possible in the finished code are limited.

I understand the pressure to get stuff done. And the problem isn't that it's happening in any one company or department, but that it's happening in *all* companies and departments.

I don't think there's any way of stopping it. Even with AI in its current form, ropey AI code is ending up in prod.

To be honest, I think the first to go will be front-end developers. The back-end is responsible for data security, so will be the last. I hope I'm being overly pessimistic, but I think both areas will be significantly reduced within the next 5 years.

The pressure to create code quickly at the expense of quality, forces devs to use AI more. If it works, then there's less pressure to hire new devs, which leads to fewer devs, which encourages the use of AI etc. Iterate that loop a few thousand times...

So instead of hiring a CSS developer, you've been incentivised to outsource their job to AI. No doubt there will be CSS developers who will be doing the same for html and javascript.
And eventually management will realise they can get something kind of workable by just feeding in the UI/UX design.

Not at all comparable. Documentation is for architecture and syntax. AI will soon be taking over the logic.

I like my job. I create elegant logical structures in my perfect universe of 1s and 0s. Within the next 5 years, a lot of that will be taken away.

A dev who needs AI at all isn't a very good dev.
But that's the problem, only about 10% of devs are good, 30% are ok, 30% are crap but might improve, and the rest have chosen the wrong career. Good devs are out numbered. To the rest, AI will level the playing field - downwards.

Eventually AI-speak will become the high-level language of choice and a developers job changes from logic and structure, to persuading an idiot machine to do what you want without making stuff up.

Developers may still be employed, but they won't be programmers

www.theregister.com/2025/04/12/a...

Developers will be incentivised to use AI code because it's quicker. From a management perspective, there's no difference between a dev writing code they don't understand or an AI doing it. But with no one who understands how or why it works, they'll become more reliant on AI to debug and update it.

I don't think I've ever got a good answer out of any of them, and trying to figure out which of its 'facts' are just made up is a pain. But why promote the use of a tool that will eventually take over your job? (albeit badly)