Live data from Hacker News

The AI coding trap

chrisloy.dev

381–390 of 424 posts

Re: The AI coding trap

#381
post #7

I would love to see an anti-AI take that doesn't hinge on the idea that technology forces people to be lazy/careless/thoughtless. The plan-build-test-reflect loop is equally important when using an LLM to generate code, as anyone who's seriously used the tech knows: if you yolo your way through a build without thought, it will collapse in on itself quickly. But if you DO apply that loop, you get to spend much more ti…

Read Eliezer Yudkowsky. He raises plenty of anti-AI arguments, none of them have to do with laziness.

Re: The AI coding trap

#382
post #371
post #337

Earlier quoted context omitted.

They wrote: They can code your startup... Like the LLM was a person, lol.

LLMs can code - different products. The plural of "It" is "They". Lol.

I didnt know, I am not native and have never seen it before

Like for example nobody says:

They cars can be fast.

People usually say:

The cars are fast.

Or sometimes:

Them cars are fast.

But never:

They cars are fast.

Re: The AI coding trap

#383

Earlier quoted context omitted.

In the micro, sure. In the macro, if you are finding architecture problems after 30 minutes, then I’m afraid you aren’t really doing architecture planning up front.

Depends on what you're building. If it's another crud app sure, but if its something remotely novel you just can't understand the landscape without walking through it at least once.

> if its something remotely novel you just can't understand the landscape without walking through it at least once

Sure you can. Mapping out the unknowns (and then having a plan to make each one knowable) is the single most important function of whoever you have designing your architecture.

Up-front architecture isn't about some all-knowing deity proclaiming the perfect architecture from on high. It's an exercise in risk management, just like any other engineering task.

Re: The AI coding trap

#384
post #325

Earlier quoted context omitted.

Most AI evangelist commenters here end up with the same arguments every time. You are just not a true scotsman. And when they link something is one of those repos full of sloop and no code. I am becoming paranoid and wonder how many people here can even code.

It is a bit funny that 4 hours on and still no replies from the evangelists. I want them to be right and me wrong! Please someone show I am wrong.

The number of projects shared is more ot less tye number of bussines that accept Ethereum

Re: The AI coding trap

#385

I agree with this. My bosses boss thinks that AI is going to end up doing 95% of our work for us. From my experience (so far) AI coding follows the 80/20 rule, it can get you 80% of what you want for 20% of the time/effort. And the ratio might be more like, it'll get you 80% of what you want IMMEDIATELY, but it can't get you the last 20%, it needs a human to get it over the finish line. It's super impressive in my op…

It depends on which application you're using. Applications like "RooCode", which is a free extension for VSCode, have several "modes" which allow the user to create an outline of the project using an "architect" LLM, followed by coding the project with a "Coding" LLM, followed by debugging the project with a "Debugging" LLM if there are bugs. There's also an LLM that answers questions about the project. Only the coding and the debugging LLMs do actual coding but you can set it so you have to approve each change it makes.

Re: The AI coding trap

#386
post #7

I would love to see an anti-AI take that doesn't hinge on the idea that technology forces people to be lazy/careless/thoughtless. The plan-build-test-reflect loop is equally important when using an LLM to generate code, as anyone who's seriously used the tech knows: if you yolo your way through a build without thought, it will collapse in on itself quickly. But if you DO apply that loop, you get to spend much more ti…

Funny that you imagine AI-coders doing any sort of thinking

Re: The AI coding trap

#387

My impression is, that AI is currently used to get rid of the junior coders, while burning out the senior coders. Later, you'll realize that there are no new senior coders to burn out, because you got rid of the junior coders, but we're not there yet.

Why should we assume that LLMs would be stagnant at current levels when, so far, they haven't stopped improving? I remember when simply using Copilot to just auto-complete 1 line of code was a groundbreaking unimaginable advancement. That was only a few years ago. New and improved models are being released nearly every week. The open-source models are nearly as advanced as the closed source models (if you have the hardware to run them at full capacity).

Re: The AI coding trap

#389
post #7

I would love to see an anti-AI take that doesn't hinge on the idea that technology forces people to be lazy/careless/thoughtless. The plan-build-test-reflect loop is equally important when using an LLM to generate code, as anyone who's seriously used the tech knows: if you yolo your way through a build without thought, it will collapse in on itself quickly. But if you DO apply that loop, you get to spend much more ti…

> I would love to see an anti-AI take that doesn't hinge on the idea that technology forces people to be lazy/careless/thoughtless. I think this might simply be how the human brain works. Take autonomous driving as an example: while the car drives on its own the human driver is supposed to be alert and step in if needed. But does that work? Or will the driver's mind wander off because the car has been driving properl…

Ah yes, finally someone who gets it. You're a smart fella.

I view the story of LLMs akin to the Concorde. Something catastrophic will happen that will be too big to ignore and all trust will implode.

Post reply on HN