Sometimes its nice for your PK to be uniformly distributed. As a reader, even if it hurts as a writer. For instance, you can easily shard queries and workloads.
> the impact to inserts and retrieval of individual items or ranges of values from the index.
I think you're taking issue with the wrong thing here lol. There may have been something before (it's the real world after all), but what RFK is doing is quite frankly insane.
oh definitely - that is why I have not commented on this part of article, as I agree that such pseudoscience is simply idiotic, dangerous and will kill people and I am in agreement that it is bad
But this part made me go "really? really? really?" - this kind of reality denial is not helpful either and prompted my comment. And they could phrase it a bit more mildly for far greater accuracy.
idk...all the Claude-generated code I'm seeing checked into our codebase is as bad as the code the same people wrote themselves. Claude probably makes it less strenuous and faster for them to produce those results though.
Uh oh.. maybe it's a problem to grease the wheels of the least-skilled...
> So how can Valve get away with this? Three things cut against the skins’ status as securities.
Small lip service at the end that acts like it's a grey area. No it's not - these are so far away from being securities it's purely superficial to even make the comparison
> the impact to inserts and retrieval of individual items or ranges of values from the index.
Classic OLTP vs OLAP.
reply