That is very cool, but Copilot is hot garbage. So I'm not sure I would cite anything they're doing as a win for LLM coding.

If this is how you use LLMs, you are the problem.

So have you never had a problem the LLM couldn't solve? What do you do in that scenario?

How do you guide the LLM away from making a horrible choice if you don't understand the internals?

I don't know, we spent the last few years with tons of posts telling us "coding is dead" and the biggest companies in the world telling us our jobs are going to go extinct.

That mindset has also deteriorated my working environment due to some coworkers buying into it.

So it's kind of nice to see some sanity checks that align with my beliefs too. I can share articles like this with my teammates. I can see that I'm not alone in thinking most LLM code is slop.

I think too junior devs NEED to see this. My team had a couple of promising juniors who are now completely brain rotted by AI and can't even write "Hello World" without consulting Claude anymore.

Yeah I agree. We're still swinging this pendulum. We haven't found the stable equilibrium yet. It's useful for people to keep having this debate.

I don't think that's true.

I don't think companies are living and dying, by how much code they can produce. Even tech companies.

They absolutely live and die by how quickly they can produce working solutions.

Well, and that's how you get enshittification everywhere. Everyone just cares about time to market, consumers are left to drown among a sea of slop, and honest businesses go down because they cannot stand a chance against slop peddlers flush with VC money.

"working solutions" is the key portion of the comment.

Pareto principle. 20% of the effort will get you the 80% happy enough with a half finished vibecoded slop.

Enshittification happens after the company was quick to deliver a working solution. They successfully captured the market, killed off the competition and now they are ready to start milking the customers who have no other choice.

AI slop can actually help with this, because it reduces the cost of replacing their enshittificated software.

The reason its hard to dethrone Facebook, Instagram, YouTube, Twitch, etc. Is not because it's hard to recreate the software (it may or may not be) it's because of network effects, budgets, etc.

Yeah! Restaurants, famously businesses who can lose customers with no downside and don't operate with a high chance of failure.

this is an idiotic take

My bet: it's less than a 2% loss in customers that are just very loud on the internet.

Given restaurant margins are in the single digit percentage points, even a 2% loss of customers could be a big deal.

> it just polls you when it needs clarification

I think anyone who has worked on a serious software project would say, this means it would be polling you constantly.

Even if we posit that an LLM is equivalent to a human, humans constantly clarify requirements/architecture. IMO on both of those fronts the correct path often reveals itself over time, rather than being knowable from the start.

So in this scenario it seems like you'd be dealing with constant pings and need to really make sure you're understanding of the project is growing with the LLM's development efforts as well.

To me this seems like the best-case of the current technology, the models have been getting better and better at doing what you tell it in small chunks but you still need to be deciding what it should be doing. These chunks don't feel as though they're getting bigger unless you're willing to accept slop.

Surely at that point they could write the code themselves faster than they can review 5 PRs.

Producing more slop for someone else to work through is not the solution you think it is.

Give your juniors reasons to stay at your company? It's not hard if the company cares at all.

>It's not hard if the company cares at all.

It's pretty hard for a non-big tech company to pay big tech level salaries.

And most of my friends and colleagues would take a full remote role that pays half what big tech, 5 days in office pays. Add in an extra week of PTO and you have a great pitch to devs.

I'll believe it when I see it reflected in applicant resumes. (east coast tech firm)

What do you mean? You’re not getting applicant resumes to your smaller org?

I personally turned down an Apple offer because they required 3 days in office and went this a much smaller fully remote team.

You can incentivize people to stay with things other than salary. Salary plays a part of course, but there is a lot of other aspects that make staying at a job worthwhile.

Yes, as much hate as it tends to get on here it's really fine. This vulnerability is unfortunate but every library/framework will have security issues over its lifespan.

The trivial nature of the initial exploit does not instil confidence, nor does it that no one noticed it during the refactor that lead to the second variation of the exploit.