mirsadm

Yes but they would have had to spend years training/practicing which apparently is not a thing we value anymore.

An older iPhone is already better than most new cheaper Android phones.

You're right to push back...

Does it? That's not even well established yet. These things aren't that good.

I'm looking at buying one now and as far as I can tell Fender seems to make shoddy quality instruments these days. I see a lot of recommendations for PRS and others.

To me it feels like they're basically tweaking these things around the edges. I'm not seeing any difference in capability just preference. This has been the case for a while.

I'd be curious to see how much CPU time is wasted on looking for a null every time strlen is called. The extra length integer is probably insignificant compared to that.

What does older mean in this context? Because some people still think the year 1996 wasn't that long ago. Modern Renault cars are fine and reliable enough. I've had 4 in my life time and had zero issues myself. I see a ton of them here in the UK and, again, they're fine.

It's the real deal. Before Fable nothing I tried worked. It has finally helped me finish my teleportation device. I can't show you or anyone the proof but trust me it's true.

What's 12 months lead time worth? Not much from what I can tell. Contrary to what these AI companies might tell you, if an AI model can't do it, a human can still do the work.

This seems pretty unlikely. If it turns out to be true then you don't need a junior or senior dev you can just get a random person from the street and they could do the job.

That is a very uninformed view. Real time CV is not going to be doing that anytime soon.

You can apply this same argument to everything. Code is deterministic but what is being made is often not because people don't know what they want to make. Society can choose just to make everything boring and deterministic so that computers can do everything.

It's gotta be booking a flight or restaurant or something. They demo this every year and it never works.

Have you tried classic CV SR algorithms (eg SR from multiple nearby frames)? Single frame SR seems unlikely to be useful.

I've built something like this. One issue is that LLMs are actually terrible at writing good shaders. I've spent way too much time trying to get them not to be so awful at it.

The way Claude/Codex behave is entirely consistent with how every vibe coded project (of mine) has ended up so far. I bet those guys have no idea what's going on and are taking guesses because no one understands the thing they've made.

How is that going to find anything that interacts across files?

The numbers only go up to 100% though.

Not in my experience. They're pretty good at getting average performance which is often better than most programmers seem to be willing to aim for.

I've noticed even experienced engineers have started overestimating how long things would take to build without AI. Believe it or not we coded before AI and not everything took years all the time.

I don't know if I agree with that. It's a struggle to get a modern compiler to vectorize a basic loop.

That is already the struggle. There is too much stuff already.

Why? Give it a couple weeks and everybody will forget about this. They'll be earning more money than previously. Job well done.

100% dependent on the person driving it

I do this all the time but then you end up with really over engineered code that has way more issues than before. Then you're back to prompting to fix a bunch of issues. If you didn't write the initial code sometimes it's difficult to know the best way to refactor it. The answer people will say is to prompt it to give you ideas. Well then you're back to it generating more and more code and every time it does a refactor it introduces more issues. These issues aren't obvious though. They're really hard to spot.

I have already been doing this. I could keep doing it but I'm not going to. I want to be able to understand my own code because that is what let's me make sound higher level decisions.

My own observation is that the initial boost to productivity results in massive crippling technical debt.

I have an app which is fairly popular. This release cycle I used Claude Code and codex to implement all the changes / features. It definitely let me move much quicker than before.

However now that it's in the beta stage the amount of issues and bugs is insane. I reviewed a lot of the code that went in as well. I suspect the bug fixing stage is going to take longer than the initial implementation. There are so many issues and my mental model of the codebase has severely degraded.

It was an interesting experiment but I don't think I would do it again this way.

Even then there is no transparency on how it decides what runs on the ANE/GPU etc