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

submitted 6 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

[-] mawhrin@awful.systems 13 points 6 months ago* (last edited 6 months ago)

they also stored this thing as a fucking string. looking up strings is costly.

[-] ChairmanMeow@programming.dev 3 points 6 months ago

This sounds like a case of premature optimization to me. We have plenty of databases using strings as Ids and they're all more than fast enough for any of our purposes. And that's with considerable volume going through.

I've never seen bad performance from string ids be an issue.

[-] sinedpick@awful.systems 14 points 6 months ago

so we're calling "not doing pointless unnecessary work" premature optimization now? cool cool

[-] 200fifty@awful.systems 13 points 6 months ago

Making me learn how to do things the right way is premature optimization

load more comments (2 replies)

load more comments (7 replies)

load more comments (9 replies)

this post was submitted on 13 Jun 2024

65 points (100.0% liked)

TechTakes

1490 readers

28 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 2 years ago

MODERATORS

dgerard@awful.systems