The new stripe.com homepage is live. 🚀
It’s been awesome to help bring it to life, and I’m really grateful to have worked alongside such an incredibly talented team!
Had an absolute blast building this with the team! www.itsnicethat.com/articles/mic...
It seems like every word and word combination you can think of is already taken on Rubygems by a 0.0.1 gem that was last published 14 years ago, has next to no downloads and the author has disappeared from the face of the earth.
Can the community come up with a better process for freeing these up?
It was indeed naive, a multi-threaded test script proved it wasn’t atomic 😕
Is something like this too naive?
get_or_set = hash[:key] ||= value
It avoids the block, but not sure about the GVL protection…
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!
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/...
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.
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!
👋🏼 I’m an #engineer at #Stripe based in #NYC, with over 10 years of experience building #frontend and #backend #webApps. My main specialty is #Ruby, but I enjoy working across the stack.
When I’m not coding, you can find me walking my #goldenRetriever or refining my unnecessarily complex #homelab!
