>In 1993, Jurassic Park came out and revolutionized the use of CGI in films I thought Terminator 2 did this. At least around where I lived everyone talked about T2 and questioned how they did this or that. JP? Not really.
Don't you mean extinct?
91–100 of 145 posts
Re: Don't you mean extinct?
#92Earlier quoted context omitted.
> I prefer spending some time to design suitable data structures/algorithms for the problem at hand. I'm doing this at LLM speed now. I feel like I'm doing the work of two whole teams and designing rock-solid software. Rust, strong types, enums, fantastic interfaces, brevity.
> Rust, strong types, enums, fantastic interfaces, brevity. That's not what suitable data structures/algorithms mean. What you stated are mere helpers and still pertains to the realms of coding, not design. Coding isn't and never was the issue. It is a tool and not the intent. Think about what would stand universally true whether you use Go, C, JavaScript, Assembly,... The organization of data (information), and the…
Re: Don't you mean extinct?
#93Earlier quoted context omitted.
This is very much an N=1 anecdote from a friend, but his manager has basically doubled velocity expectations for the team at his company over the last year. Everyone has to use Claude code because that's the only model they're allowed to use, and not using it means not hitting the arbitrary expectations. Conversely, the company I am at has no such expectations, and we've got a legacy code base that LLMs aren't very h…
we've got a legacy code base that LLMs aren't very handy in anyway So do I. What I'm finding is that they are now. I've spent the last week tracking down bugs using Fable that have gone undiagnosed for several years. And this is a damned obscure legacy code base that runs on a proprietary 8051 variant. Guaranteed to be nothing like it in-distribution.
Re: Don't you mean extinct?
#94Earlier quoted context omitted.
My biggest gripe with AI is that I struggle to come up with even one real problem that it has solved in my daily life, and that of my family and friends. Yes it might have made me a bit faster at some things I do for work. But it seems to me that we face so many challenges as a civilization, and AI doesn’t actively help with any of them? Unless you buy into the narrative that it will somehow usher in a golden age of…
> My biggest gripe with AI is that I struggle to come up with even one real problem that it has solved in my daily life, and that of my family and friends. I wish I could upvote this a thousand times, because this is exactly my experience as well. It's made a few things slightly more convenient , but convenience is not exactly a problem in my life! And yet, it's actively damaging a lot of things I care about in a way…
Re: Don't you mean extinct?
#95This analogy has layers that OP probably doesn't recognize. The film industry loves cgi because none of the digital vfx houses are unionized and they can treat the artists like crap. It severely devalued a ton of skilled labor around miniature and set design. Now, after 20 years of hard swing into cgi, people are starting to recognize just how much better movies from the practical era looked, and there is a push back…
You can have the most everyday-setting movie or TV show imaginable and still have it VFX'd to hell and back compared to something shot on film 30 years ago. Not even just like Ted Lasso faking the stadiums/fields they were on, but just retouching every single little thing.
Re: Don't you mean extinct?
#96Earlier quoted context omitted.
You can accomplish quite a lot with smaller local models on reasonably priced pro tier hardware (not cheap hardware, but very attainable hardware for anyone making average software engineer money). Qwen 3.6 27B and 35BA3, Gemma 28B, and so on are incredibly beneficial even if Anthropic and OpenAI produce better options. Failing that, GLM 5.2 is open weights, trades blows with current frontier models and widely availa…
Why pay for hardware for local model when you have a working local brain?
Re: Don't you mean extinct?
#97Earlier quoted context omitted.
Those times are passing and you'll sooner or later meet with new reality.
I think a lot of HN'ers are in denial. I was an LLM skeptic check my history if you like. At the beginning of 2026 LLMs shifted over the hump to as good or better than most devs and are continuing to get better. I don't think we've even begun to see how this is going to affect the industry. People in charge don't and never have cared about code quality, tech debt, maintainability. Now they will not only not care but…
They will just generate code that passes the tests also written by the AI, ask the AI to find any bugs, and so long as the code runs without obvious issues, that will get released.
Re: Don't you mean extinct?
#98Earlier quoted context omitted.
> Rust, strong types, enums, fantastic interfaces, brevity. That's not what suitable data structures/algorithms mean. What you stated are mere helpers and still pertains to the realms of coding, not design. Coding isn't and never was the issue. It is a tool and not the intent. Think about what would stand universally true whether you use Go, C, JavaScript, Assembly,... The organization of data (information), and the…
No but it lets you iterate faster. Who hasn't come up wit the most perfect elegant design, only to come up against three reality of implement and an "oh we forgot about that" aspect. Except by then, it's too late to change, so you march on. Writing code faster lets you find the things you didn't think of faster so then you get to design it again but better this time.
Re: Don't you mean extinct?
#99Re: Don't you mean extinct?
#100Earlier quoted context omitted.
> Rust, strong types, enums, fantastic interfaces, brevity. That's not what suitable data structures/algorithms mean. What you stated are mere helpers and still pertains to the realms of coding, not design. Coding isn't and never was the issue. It is a tool and not the intent. Think about what would stand universally true whether you use Go, C, JavaScript, Assembly,... The organization of data (information), and the…
No but it lets you iterate faster. Who hasn't come up wit the most perfect elegant design, only to come up against three reality of implement and an "oh we forgot about that" aspect. Except by then, it's too late to change, so you march on. Writing code faster lets you find the things you didn't think of faster so then you get to design it again but better this time.
The mistake here is trying to come up with the most elegant design. You solve for what’s needed with the knowledge that you’ve most likely not captured the full situation, and make allowance for future changes.
I don’t want faster code. What I want is flexibility in evolving my design and there’s plenty of good tools and practices for that. From ensuring your code is testable to ensuring there are easy ways to experiment with parts of it.
I’ve never been in a situation that says “We’ve not think of that, we need to get back to the drawing board”, It’s been mostly “We need a new version of this module to support this feature”