is it considered acceptable journalistic ethics at Vox for a journalist who reports on EAs and prediction markets to make prediction market bets on how a journalistic outlet will follow-up a story on prediction markets and EAs? My eyebrows have just levitated so high they've collided with a starlink swarm.
gnomicutterance
joined 5 months ago
Imagine saying “we have no specific views on eugenics”! You should, buddy. You should.
Solutions: AI-guided suggestions to parents about the traits they should select
There’s a joke in here about and that’s how the human race all became polydactylic with extra elbows, but it’s too early in the morning for me to figure out how to make it not be at the expense of people with limb and facial differences.
ah, thank you!
when you do not yet have (1) customers, (B) unit tests, (ג) developers who can write their own code, or (IV) exception handling, the term-of-art that comes to mind for doing anything besides auto-incrementing primary keys is YAGNI. (Especially because nobody who is making thoughtful, careful database tuning decisions is using chat-gippity to convert their models. And more to the point, they aren't using SQLAlchemy of all things to make large, distributed applications that need UUID primary keys.)
okay, for some reason, I feel the need to help.
The given link defines the function that creates a UUID:
uuid.uuid4(): Generate a random UUID.
In mathematics, can you generate a monotonic function by generating random numbers?
There are countless issues here. They didn't do exception handling, they used a string to store their UUIDs (even if this was a DB constraint, you use sqlalchemy.Uuid and let the ORM and DB handle the translation), and as the person you're replying to stressed, they're using non-monotonic UUIDs. Also if you have a unique user_id and you're never exposing your primary keys, you don't need to get fancy, just let the ORM handle it with auto-incrementing, for most use cases. And so many other tragic things about this one tiny blog post.
tl;dr if you're going to copy code you don't understand, copy it from the docs, not from everything in the kitchen thrown into a blender.
If you’re using a new-to-you ORM, and you don’t ever check the docs to see the basic primary key syntax… it’s SQLAchemy, it’s well documented and there’s tons of prior art.
Also I don’t understand their business case but if a user has a primary key, a unique user ID, and a unique customer ID, then all three of those uniquely identify the customer. (Weird, but there are some plausible explanations.) But then why would you need both the user ID and the customer ID in the subscription table is this some stripe thing I don’t understand or are they just bad at this?
It’s okay to copy/paste your basic model structure for SQLAlchemy classes, but copy and paste from the SQLAlchemy docs. Sweet suffering stack overflow, did nobody even look at the docs ever, or did they only trust ChatGPT? SQLAlchemy‘s simple for basic use cases.
Also here is such a nutshell of everything wrong with YC: jackhole prompt fondlers with no tests, no paying customers, who turn on the most important new feature in prod at the end of the day (jesus wept), and yet with all that clown show,
We had eight ECS tasks on AWS, all running five instances of our backend (overkill, yes we know, but to be fair we had AWS credits).
What the actual fuck.
But betting? There’s being an insider and then there’s profiting, and aren’t most journalists prohibited from trading or betting on their covered areas?