But this question posed to humans is plenty ambiguous because it doesn't specify whether you need to get to the boat or not, and whether or not the boat is at the wash already. ChatGPT Free Tier handles the ambiguity, note the finishing remark:

"If the boat wash is 50 meters down the street…

Drive? By the time you start the engine, you’re already there.

Sail? Unless there’s a canal running down your street, that’s going to be a very short and very awkward voyage.

Walk? You’ll be there in about 40 seconds.

The obvious winner is walk — unless this is a trick question and your yacht is currently parked in your living room.

If your yacht is already in the water and the wash is dock-accessible, then you’d idle it over. But if you’re just going there to arrange detailing, definitely walk."

The original car question is not ambiguous at all. And the specific responses to the car question weren't even concerned with ambiguity at all, the logic was borderline LLM psychosis in some examples like you'd see in GPT 3.5 but papered over by the well-spoken "intelligence" of a modern SOTA model.

If we take the post as truth (it's not clear to me whether we can), then Bazzite will get iffy kernel updates that will particularly break handhelds. But desktop will be more stable and you could even turn off automatic updates for 6months and see how things look after.

I think Bazzite has a very smooth experience for Windows gaming and even if you decide that you don't like it or that the distro really is falling apart, you'll have gotten the best Linux-gaming experience and can evaluate other distros more clearly.

Scott Adams taught ChatGPT to put humans into an instant bliss-state. "Seems at least plausible"?

The blog is not terrible advice, but "getting promoted" just seems like a waste of time and effort nowadays. To get promoted at Google from L5 (Sr SWE) to L6 (Staff SWE) you need to do the work of a GOOD L6 for 1y+ and have made some very solid internal networking connections and have multiple managers on your side and have an opening for such a role.

To get hired away from Google to an L6-equivalent role at Meta (or whereever) you need to get halfway through one L6 project and do a few hours of interviewing. There's no comparison in the level of effort. (And I'm not picking on Google here. I think it's the same or worse nearly everywhere.)

The 85%ile of L used to be above that of the lowest 15%ile of L+1 so in the year that you demonstrate L+1 you'll get compensated as L+1.

Now, the 85%ile of L is less than that of the lowest 15%ile of L+1 so until you actually get promoted there's no real compensation difference. Which makes leaving for L+1 so much more attractive (and also going above-and-beyond less attractive).

100% agreed. Just as importantly, you also need to be aware of what type of an environment you are in and plan accordingly.

Sometimes, you are just in an environment where it is somewhere between extremely improbable and nearly impossible to get promoted. At that point, you would be better served to put more effort into changing that environment, instead of chasing the grind. I learned that one the hard way a few years ago, at, ironically, Google.

I was on track to a promo, got a documented track record, got the backing of multiple managers + my team lead, etc. But guess what? Another reorg happened shortly before the cutoff for the review cycle, i got a new manager who literally just met me for the first time, and my chances tanked to essentially zero (which is understandable, because I don’t see how a manager who just discovered my existence a week prior would be able to effectively back my promo package). Since then, I had an average of 3-5 major reorgs and 1-2 manager changes per year. As I came to eventually realize, this type of a dysfunctional environment wasn’t conductive to a good career velocity.

Needless to say, my decision to just put my head in the sand and grind harder to compensate for this kind of organizational instability was stupid. It would’ve definitely been a better bet (in terms of time/effort, career trajectory, and compensation) to put even just a portion of that effort into changing my environment, as opposed to trying to compensate for organizational dysfunction with raw work effort.

TLDR: if you care about having a good promotion velocity, focus on the biggest blocker in your specific situation. Whether it is the lack of track record demonstrating sustained effort at the L+1 level, or your environment being dysfunctional in ways that make promotions improbable, etc. Just gotta keep the eyes on the prize, and pick the solutions that are the most appropriate for your individual situation (instead of blindly just doing "XYZ because I read that it was a great career advice" in a single-minded manner).

You can generate videos locally. The models anlready exist.

> “Can I use any language?” > > “Sure.” > > Move quickly, before he realizes his mistake.

I’m almost serious, the only time I saw haskell in production was after a similar scenario.

Your use-case is totally different: "I want this job to run at this time" so the only lesson that applies to you is that the `cron` utility might behave weird during DST switches. No idea if it underlies your cloud provider, so it may be completely irrelevant.