TechTakes

1436 readers

135 users here now

Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.

This is not debate club. Unless it’s amusing debate.

For actually-good tech, you want our NotAwfulTech community

founded 1 year ago

MODERATORS

dgerard@awful.systems

using GitHub CoPilot leads to the obvious consequence (archive.is)

submitted 5 months ago by dgerard@awful.systems to c/techtakes@awful.systems

66 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Hexarei@programming.dev 8 points 5 months ago (1 children)

Whoops, I flubbed that message hard and didn't catch it at the time: Meant to say "don't use centralized databases." They definitely use databases lmao. No idea how I screwed that message up so hard. I blame ADHD for not proofreading.

Just so we're on the same page, let me be more specific. I'm saying the individuals in the article were making terrible decisions. Lots of them.

I am also saying that UUIDs are good primary keys for very specific purposes: Large, distributed systems that handle large amounts of small data, powered by databases like Cassandra that are designed to handle millions of record insertions per hour across several hundred nodes, to the point where inserts are very likely to happen at the exact same time on two different replicas of the same schema.

Hope that makes more sense than my previous flub. lol

[–] ebu@awful.systems 5 points 5 months ago* (last edited 5 months ago)

okay that's a little more sensible lol

i think the original comment that this thread is in reply to is avoiding non-monotonic UUIDs. i don't think anyone is contesting that autoincrementing ints create headaches when trying to distribute the database