Cristian Rivera
cristianrivera.com
Cristian Rivera
@cristianrivera.com
💼 Engineer at #Stripe | Based in #NYC
💎 10+ Years Crafting #Ruby #WebApps
🧪 #Homelab & 🏗️ #3DPrinting Enthusiast
It was indeed naive, a multi-threaded test script proved it wasn’t atomic 😕
March 12, 2025 at 7:07 PM
Is something like this too naive?

get_or_set = hash[:key] ||= value

It avoids the block, but not sure about the GVL protection…
March 12, 2025 at 7:03 PM
It will loop endlessly between :waxing_crescent and :third_quarter and never back to :new_moon, which would otherwise finally return from the loop.

Line 8 should be changed from waxing to waning!
January 22, 2025 at 12:05 AM
Wondering how much we can read into this and take them at their word.

Specifically “How do I turn off model training (ie. “Improve the model for everyone”)?”

help.openai.com/en/articles/...
Data Controls FAQ | OpenAI Help Center
help.openai.com
January 5, 2025 at 8:20 PM
Though in your follow up example where you’re taking in attributes of an entity such as a Person, I think all Keyword arguments are best.
November 19, 2024 at 12:19 AM
It depends, but usually:

- Positional arguments if there’s only one argument.
- Positional argument for the main argument along with Keyword arguments for additional, optional arguments.

I avoid relying on Positional arguments when there are multiple arguments unless their meaning is very clear!
November 19, 2024 at 12:17 AM