Hacker News new | ask | show | jobs
by groceryheist 67 days ago
Claude Code is rare product that is both beneficial and economically addictive, where its use increases demand for itself, at least in the supply / demand range for code we are accustomed to. It makes making software so much easier that Claude coding custom software becomes a solution to all sorts of past annoyances. Maintaining the software is easy enough thanks to Claude code.
2 comments

> Claude Code is rare product that is both beneficial and economically addictive,

I'm in the film and engineering spaces, and I can honestly say the same about image and video models.

There is so much fun in all of these tools, and the productivity gains are insane.

I shoot film, but I never would have been able to do anything like this before:

https://www.youtube.com/watch?v=HDdsKJl92H4

https://www.youtube.com/watch?v=oqoCWdOwr2U

Today, I saw AI OR DIE with this banger:

https://www.youtube.com/watch?v=CNbmoVdirxw

Gossip Goblin is doing incredible work as usual. Dude is a savant and would have killed it in Hollywood if he'd had a chance before:

https://www.youtube.com/watch?v=-Rzl7nUdEs4

Corridor Crew is leaning in and building new tools:

https://www.youtube.com/watch?v=Y3Dfw969itU

There's just so much incredible stuff being made by really brilliant people that never would have had the chance before. And these tools are literally brand spanking new. We're just getting started.

That's my view too. I love what people are doing with this stuff. I really want to get a decent rig to start doing this stuff locally someday.
Thanks, these are a real trip, especially loved Pi Hard.
Uh, how is this possible? Is this all Veo 3? How are they getting such fantastic continuity across clips?
Veo 3 is one of the weaker video models, surprisingly!

Google and OpenAI are both really far behind the Chinese at this point. Perhaps Google will unveil something groundbreaking at Google I/O, but both companies have been trailing for well over a year at this point.

One of the reasons OpenAI gave up was not only were they losing money, but they were also ridiculously far behind (11th or below in the rankings).

The models most professionals use are Kling o3, Kling 3.0 and, more recently, Seedance 2.0. These are all Chinese models.

Seedance 2.0 stands out as an almost order of magnitude improvement over everything else in the industry. It's truly the SOTA model. It blows everything else out of the water, and it's truly remarkable to experience it in use.

On April 30th, Alibaba's new Happy Horse model rolls out. They poached folks from Kling to build it. It's supposedly 2-5x cheaper than Seedance 2.0, and its ELO scores rank it as the new highest performing model.

https://artificialanalysis.ai/video/leaderboard/text-to-vide...

https://artificialanalysis.ai/video/leaderboard/image-to-vid...

They aren't one shotting these.
You would be surprised.

Some shots are indeed impossible to one shot, but others can serendipitously turn out better than you wanted.

I'd say it averages 2.5 generations per shot. A lot of single one off one shots, and some (few) shots that just won't work no matter how hard you prompt.

That said, it's likely you'll find usable footage even in the losses. Videos are meant to be cut. A failed generation might still have salvageable contents you can cut to/from.

Editors are the super powered folks in AI video.

I have now witnessed first hand what the unexpected benefits might be. I expected CC to be a boon to overburdened teams, because it's now possible to spend $2 on compute and have it write a mostly-one-off tool that nobody would ever otherwise have the capacity or time for.

Sure, that's happening too, but to a lesser degree than I thought. CC with a number of "enterprise integrations" (really: corporate MCPs) is a pretty hefty force-multiplier for operations teams. "Go summarise and dissect this weird client request for me. Documentation is spread across at least $THESE_ENTERPRISE_DATA_SILOES." Saves a bunch of time pinging the different people across continents who happen to know intimate details. That was not entirely unexpected.

It's the technically minded but not necessarily otherwise technical people who keep surprising me in weird and wacky ways. People are building themselves and their immediate peers disposable dashboards. Who needs a service to pull data for a real-time display when CC can collect the necessary information and construct a local, static HTML file with all the info neatly in one place? I'm sure there will be a hangover because the compute cost for doing these in JIT fashion will surely feel like death by a thousand cuts at some point, but the ability to really quickly validate whether certain types of data aggregations are useful is proving to be ... a positive development.

I disagree about the ease of maintaining the software, though. You still need the skills to really understand what the code is doing, and with the original "why" possibly lost in the adrenaline haze, the maintenance effort floor has shifted.