Yes. My take is that meta and others want this lawsuit to happen this way because they can use it as an excuse for age verification and other tracking things going on ATM too. The fine is nothing to them, but this is justification require more user identification
What you can do locally is slower and with much smaller models.
Ya absolutely, I never want a fuel exhaustion event. Always put more in than necessary
I had not heard that, thank you for sharing. I just go by IFR standards or better for my personal limits, so this never came up.
I’ve never seen a rule requiring any specific fuel reserve except for when filing IFR where you need enough fuel to get to your destination, and alternate, and still have 45 minutes of fuel.
Every manager can expense what they want if they can get their manager to support it, so some offices (or more realistically, some teams in some offices) have nicer perks than others, but GREF doesn’t provide anything for free. If she was getting free food, that was her management chain doing that, not amazon as a whole (unlike say Google or meta that has free cafeterias, I’ve never seen a cafeteria in Amazon with free food).
Amazon has never been like that, Google has had more perks like that in the past, but Amazon has always been much more frugal.
Ya I’m finding myself being the bad code generator at work as I’m scattered across so many things at the moment due to attrition and AI can do a lot of the boilerplate work, but it’s such a time and energy sink to fully review what it generates and I’ve found basic things I missed that others catch and shows the sloppiness. I usually take pride in my code, but I have no attachment to what’s generated and that’s exposing issues with trying to scale out using this