Live data from Hacker News

Firing programmers for AI is a mistake

defragzone.substack.com

211–220 of 886 posts

Re: Firing programmers for AI is a mistake

#211

If there will be actual AGI (or super intelligence), none of these arguments hold. The machines will just be better than any programmer money can buy. Of course at that point every knowledge worker is probably unemployable anyway.

What if AGI is extremely expensive to run?

then we ask AGI how to make itself less expensive to run

Re: Firing programmers for AI is a mistake

#212
post #11

We have fired all our programmers. However, the AI is hard to work with, it expects specific wording in order to program our code as expected. We have hired people with expertise in the specific language needed to transmit our specifications to the AI with more precision.

I think people aren't getting your joke.

Now we are!

Re: Firing programmers for AI is a mistake

#213
post #144

There's such a huge disconnect between people reading headlines and developers who are actually trying to use AI day to day in good faith. We know what it is good at and what it's not. It's incredibly far away from doing any significant change in a mature codebase. In fact I've become so bearish on the technology trying to use it for this, I'm thinking there's going to have to be some other breakthrough or something…

Yes. I think part of the problem is how good it is at starting from a blank slate and putting together an MVP type app. As a developer, I have been thoroughly impressed by this. Then non-devs see this and must think software engineers are doomed. What they don't see is how terrible LLMs are at working with complex, mature codebases and the hallucinations and endless feedback loops that go with that.

The tech to quickly spin up MVP apps has been around for a while now. It gets you from a troubling blank slate to something with structure, something you can shape and build on.

I am of course talking about

  npx create-{template name}
Or your language of choice's equivalent (or git clone template-repo).

Re: Firing programmers for AI is a mistake

#214
post #144

There's such a huge disconnect between people reading headlines and developers who are actually trying to use AI day to day in good faith. We know what it is good at and what it's not. It's incredibly far away from doing any significant change in a mature codebase. In fact I've become so bearish on the technology trying to use it for this, I'm thinking there's going to have to be some other breakthrough or something…

I think that LLMs are only going to make people with real tech/programming skills much more in demand, as younger programmers skip straight into prompt engineering and never develop themselves technically beyond the bare minimum needed to glue things together.

The gap between people with deep, hands-on experience that understand how a computer works and prompt engineers will become so insanely deep.

Somebody needs to write that operating system the LLM runs on. Or your bank's backend system that securely stores your money. Or the mission critical systems powering this airplane you're flying next week... to pretend like this will all be handled by LLMs is so insanely out of touch with reality.

Re: Firing programmers for AI is a mistake

#215
post #144

There's such a huge disconnect between people reading headlines and developers who are actually trying to use AI day to day in good faith. We know what it is good at and what it's not. It's incredibly far away from doing any significant change in a mature codebase. In fact I've become so bearish on the technology trying to use it for this, I'm thinking there's going to have to be some other breakthrough or something…

> It's incredibly far away from doing any significant change in a mature codebase The COBOL crisis at Y2K comes to mind.

Is this the same Cobol crisis we have now?

https://www.computerweekly.com/news/366588232/Cobol-knowledg...

Re: Firing programmers for AI is a mistake

#216

Earlier quoted context omitted.

Part of the problem is that many working developers are still in companies that don't allow experimentation with the bleeding edge of AI on their code base, so their experiences come from headlines and from playing around on personal projects. And on the first 10,000 lines of code, the best in class tools are actually pretty good. Since they can help define the structure of the code, it ends up shaped in a way that w…

My company allowed us to use it but most developers around me didn't reach out to the correct people to be able to use it. Yes I find it incredibly helpful and try to tell them. But it's only helpful in small contexts, auto completing things, small snippets, generating small functions. Any large scale changes like most of these AI companies try to push them being capable of doing it just falls straight on its face. I…

Did you have to do any preparation steps before you asked from a model to do the large scale change or there were no steps involved? For example, did you simply ask for the change or did you give a model a chance to learn about the codebase. I am genuinely asking, I'm curious because I haven't had a chance to use those models at work.

Re: Firing programmers for AI is a mistake

#217
post #144

There's such a huge disconnect between people reading headlines and developers who are actually trying to use AI day to day in good faith. We know what it is good at and what it's not. It's incredibly far away from doing any significant change in a mature codebase. In fact I've become so bearish on the technology trying to use it for this, I'm thinking there's going to have to be some other breakthrough or something…

[dead]

Re: Firing programmers for AI is a mistake

#219
As a software engineer with about 4 years of experience, what can I do to avoid being left behind?

The author mentions "systems programming" and "high-performance computing". Do you have any resources for that (whether it be books, videos, courses)?

Re: Firing programmers for AI is a mistake

#220
I think a more interesting question is what the impact will be on the next generation looking at CS/SWE as a potential profession. It's been considered a pretty "safe" profession for a long time now. That will change over the next 10 years. Will parents advise their kids to avoid CS because the job market will be so much smaller in 10 years' time?
Post reply on HN