- veonik parentNot sure about Google but Apple has per-app time limits, per-app type time limits, overall screen time limits, time of day limits, parental review before app install, parental review before purchases can be made, etc. I've found it to be quite robust in managing my kids' access to the internet.
- I have had fairly bad luck specifying the JSONSchema for my structured outputs with Gemini. It seems like describing the schema with natural language descriptions works much better, though I do admit to needing that retry hack at times. Do you have any tips on getting the most out of a schema definition?
- To add to the confusion, you can also just use Gemini via API (without Vertex AI). It shows up as a separate item in billing.
In the (latest, of three different) Go SDK, you can use either Vertex AI or Gemini. But not all features exist in either. Gemini can use uploaded files as attachments, and Vertex AI can use RAG stores, for example. Gemini uses API key based authentication, while Vertex AI uses the traditional credentials. All in the same SDK.
It's a mess.
- Yep, that whole example after the float cast is bit silly. After the cast, the value can never be an empty string, or null. Not to mention, comparing a floating point value to an arbitrary, literal value (of zero in this case) is potentially problematic [1].
[1]: See the warning on this page, this applies to all languages with floating point arithmetic. https://www.php.net/manual/en/language.types.float.php
- For what it's worth, I actually agree. See: Curiosity or Ingenuity, both relatively new and far outperforming their expected life. Not to mention that I'm sure the ground-based transmitters that were used to actually fix Voyager 2 are likely not old, so it really isn't a case of "old is good" which helped in this case.
My comment is unfortunately an example where I let my late night shit-posting bleed over into HN, which is always regretted in the morning. Apologies ;)
- There's definitely some ambiguity there, that's a good point.
I'd probably say that users_facts would be a to-many join table between users and facts, like if you had one row per fact and a multiple facts per user though that example doesn't really make sense here (could just have the FK exist in Fact and not need a join table). If UserFacts were stored in a table with multiple facts in one row about a single user, I would probably call that table user_facts.
Would probably also be fine with running across either in any codebase (or even singular table names, for that matter! as long as it's consistent :D )
- I wrote a top level comment but I really don't understand this argument. Just because the model is "multiple facts about a user" does not mean you have to jump through hoops to name the database table. It would just be user_facts, wouldn't it? That seems intuitive and straightforward to me, even if the class name is also plural.
- Some of these arguments are a little questionable imo.
"It reads well everywhere else in the SQL query:"
You can alias the table names and have it read well in all places, and this mostly only matters if you are actually writing SQL and not using an ORM directly, which the next point seems to imply you would be using.
"The name of the class you’ll store the data into is singular (User). You therefore have a mismatch, and in ORMs (e.g., Rails) they often automatically pluralize, with the predictable result of seeing tables with names like addresss."
Almost any modern "pluralize" implementation would handle this correctly. Rails would call the table `addresses`.
"Some relations are already plural. Say you have a class called UserFacts that store miscellaneous information about a user, like age and favorite color. What will you call the database table?"
You would call the table user_facts... Am I missing something?
- The point is that lawyers sent the cease and desist, so the other side does have lawyers at their beck and call. If you want to do anything other than what they demand you do, you are risking more lawyery-action. And even if you do comply, that doesn't stop them from continuing to bring action against you for some other reason, or for damages, or whatever they want, really.
It may not be a system that is geared towards fair play, but if you want to play at all, you really should have a lawyer, too.
- It can be hard to figure out which is which for the company before getting hired though. Asking about programs that encourage PTO is a good way that I've found to suss out these types of details.
My current job offers a few "extra" things on top of unlimited PTO like during the summer, a $100 bonus if you post a pic of some activity you did on PTO (literally anything, and can even opt out of sharing if you are so inclined) or more recently, a "competition" for the best use of PTO. I think someone reading a book in a hammock won.
- WiFi calling is multicast, I think, so your phone just basically broadcasts it to the network and every device will see it, though only your router will actually do anything with it.
There's examples of WiFi calling causing this type of issue, described as a packet storm. For example, here's a reddit post with similar symptoms you're describing. https://www.reddit.com/r/networking/comments/3g31mc/iphone_w...
- Real Engineering did a video about this[0] and mentioned that SLS was really just a way to create jobs that happens to result in a massive rocket at the end. This makes sense to me and neatly explains the apparently intentionally overblown budget.