deltaburnt

Yeah I meant less that 3D games were invented out of nowhere when the PS1 or N64 released. It's more that a large majority of developers, especially ones on console, were thrust from 2D to 3D development.

I often think about how crazy it must have been to be a game developer around this period. Almost every bit of design, math, coding knowledge was flipped on its head. Overnight developers who were managing relatively simple XY coordinates suddenly had to discover the complexities of 3D rotations, perspective math, and probably more linear algebra than they ever really expected to know.

It’s even crazier we got masterpieces like Mario 64 so early into the first 3D console generation.

LLMs aren't nearly mature or deterministic enough to earn that distinction. I've had an agent tell me it read a link I gave it, when actually it lied. I don't see how you could possibly compare that to a compiler where thinking "maybe it's a compiler bug" means you've almost certainly missed something.

I think the kind of surface level rewrites that people rag on are pretty rare, at least in my experience. Realistically code that's impossible to understand, underdocumented, and lacking in proper abstractions is also deficient code. If you've ensured that the code is "good enough", you will likely hit a bug or feature request that is hindered by the poor structure and understanding of the code.

It's totally fine to say "the code works, that area is stable, let's not mess with that code". I make those kinds of tradeoffs on a near daily basis. But let's be real, "perfectly functioning code" is an ill defined, moving target. What looks like perfectly functioning code to a sibling team or a PM, could be a massive liability to someone who actually knows the code.

But then again I'm writing OS and performance critical code. A 1 in 1 million bug is easier to ignore in a throwaway log viewer website.

I don't think we should use webdev as an example of why lossy copy and paste works for the industry.

For pretty much every single person you or I personally know, that would be the equivalent of the end of humanity.

Let’s not nitpick here. Worldwide human suffering and tragedy is equivalent to the end of humanity for most.

We can sit here and armchair while in the most prosperous, comfortable era of human history. But we also have to recognize that this era is a blip of time in history. That is a lot of data showing humanity surviving sure. But it’s also a very small amount of data showing any kind of life most would want to live in.

This is a pretty discriminatory comment that I’ve honestly seen zero hint of in reality. And this is coming from someone who didn't go to a particularly prestigious school. I honestly rarely even find out what school my colleagues went to school. But the ones I know who did go to those prestigious schools are beyond humble.

Much less money lost, but Amazon is notorious for not providing free game codes that are supposed to be included with GPU purchases. The customer rep at first apologized and offered a small refund (less than the cost of the game). A later rep started implying I was trying to defraud Amazon.

Many people online share similar experiences. Wonder how much money this wide-scale fraud saves them.

Basically locks you out of HDR, high frame rates, VRR, or (more importantly) new panel technology like OLED.

I don't really buy your premise. What you're suggesting is that all code has bugs, and those bugs have equal severity and distribution regardless of any forethought or rigor put into the code.

You're right, human review and thorough design are a poor approximation of proving assumptions about your code. Yes bugs still exist. No you won't be able to prove the correctness of your code.

However, I can pretty confidently assume that malloc will work when I call it. I can pretty confidently assume that my thoroughly tested linked list will work when I call it. I can pretty confidently assume that following RAII will avoid most memory leaks.

Not all software needs meticulous careful human review. But I believe that the compounding cost of abstractions being lost and invariants being given up can be massive. I don't see any other way to attempt to maintain those other than human review or proven correctness.

In this context I meant throwaway as "low stakes" not "meaningless". Again, evaluating the output of a database import like that could be existensial for your company given the context. Not to mention there's many cases where evaluating the output isn't feasible for a human.

I don’t think I’ve ever seen someone seriously argue that personal throwaway projects need thorough code reviews of their vibe code. The problem comes in when I’m maintaining a 20 year old code base used by anywhere from 1M to 1B users.

In other words you can’t vibe code in an environment where evaluating “does this code work” is an existential question. This is the case where 7k LOC/day becomes terrifying.

Until we get much better at automatically proving correctness of programs we will need review.

Does Taiwan not have healthcare? Verbatim from Wikipedia:

> According to the Numbeo Health Care Index in 2025, Taiwan has the best healthcare system in the world, scoring 86.5 out of 100,[6] a slight increase from 86 the previous year.[7] This marked the seventh consecutive year that Taiwan has ranked first in the Numbeo Health Care Index.[8]

Literally everything will say AI generated to avoid potential liability. You'll have a "known to the state of California to cause cancer" situation.

Thank you for sharing this holy crap. I have this exact monitor and that popup drives me absolutely insane.