Funnily I see the same argument made within coding circles. AI will fully automate *that* sort of coding, but not it’s not good enough for my specialism. I’m sure the AI devs are thinking that too, but I don’t think that makes it true.
Funnily I see the same argument made within coding circles. AI will fully automate *that* sort of coding, but not it’s not good enough for my specialism. I’m sure the AI devs are thinking that too, but I don’t think that makes it true.
Backend devs say it’ll do the UI stuff because that’s just boilerplate and standard colours, but never their work because they need to really understand the architecture. UI devs say it can’t do their work because they have to really understand the users, but it’ll do the plumbing work fine.
In practice the actual code is a fairly small part of either job (and the AI isn’t even *that* good at the code part).
I think it’s more an established human mistake that skilled work looks simple from a distance. For example, policy making looks pretty simple to me. I’ve got ideas, I could probably write those up in a doc, link some sources, publish it somewhere. I bet it’s not that easy in reality though?
Where I’ve seen damage to the hiring rates (and the job market is rough at the moment) that’s from uncertainty. It’s not so much that AI is replacing all software devs, it’s that it might replace some of them. No one’s sure how many, or which ones.
So for now it’s easier to fund an AI pilot than a new hire. If the pilot doesn’t work out then we can always hire next year instead.