awildfivreld

Up until "Each guess may look reasonable on its own. But guessing itself has four problems." I read the occasional tell, but not much.

By the end of that paragraph thereafter I started skimming as the rest turned blatantly LLM.

I should have caught the emdash in the first code block in "Who else is calling" though...

The maintainers of requests have made it pretty clear that they consider that package feature complete, and have not showed interest in adding native async support to the core.

If anyone here wants to do this but don't want to implement all of this yourselves, this "field" is called Durable Execution. Frameworks such as Temporal, Restate and DBOS do a lot of the heavy lifting to get the idempotency, exactly once and recovery to a known state logic here.

But a family of 4 is not the value proposition here. They are explicitly targeting frequent flyers that stand in the queue so often that the time saves add up.

If you're only traveling once a year, you can handle a 45 minute wait twice (although yes, it still sucks). If you're traveling once a week, it's a completely different ballpark.

> and suddenly the manager walks on to the pitch and says, “OK, gather around! Where did you kick the ball yesterday? Where are you planning on kicking it today? Any blockers?”

There are sports, like handball, where each coach can call a very short timeout at more or less any time during the game for exactly this purpose. The team and coach gets to spend a minute together to adjust their tactics on the fly, based on what is working, and what isn't.

Otherwise, I agree with the conclusion of this piece, that a manager/leader should tailor their meeting(s) to what is required for their specific team to work best. If the team consists of people that all pro-actively communicate, then the meeting might not be needed. If the team has problems with making deliveries on time, then slightly more shepherding is perhaps needed.

This article is talking about elementary, middle and high schools in Oslo municipality. The grant you're talking about is for higher education nation wide.

Even still, they use quite a lot of money too.

I do. There has been no major coverage of Teslas dying in the cold.

Charging takes longer yes, and some chargers/vehicles may occasionally malfunction, but nothing newsworthy.

In a perfect world, I agree that the average user/developer would be conscious of this, and take everything from an LLM with a grain of salt.

However, I've since come to realize that too many people either just won't care about the implications, or are oblivious of them. I've come to realize that, in practice, relying on the user behaving adequately is going to create too much damage to rely on.

I'm a software developer.

There is a chicken and the egg problem when it comes to designing these things.

I can ask "What do you want the dashboard to look like" and they'll answer "I don't know before I see the data".

Then I'll ask what data they want to see, and they'll respond "What will it look like?", or we'll spend significant time on data collection only to find they never actually want it in a dashboard after all.

By far and away the most time consuming aspect of this entire domain is to find out what users actually want to see, as they almost never have something specific enough when they approach me.

Well, they do (figuratively). That is why the entire airspace is not totally shut down, but capacity "just" substantially reduced.

I know there is a rather large culture difference, but here in Norway the unions announce the start time of the strike some time before the actual walkout, instead of "you're striking right now".

If the employees here (and in the OP) did the same, they could start the strike by the end of one workday, so that no food/cement would be wasted as it it was never prepared.

Is this not possible in the US? Or is this a case of increasing one-uppance as the relationship between companies and employees is _that bad_?

* This war of mine.

While it does take place in a war zone, you play from the perspective of the civilians that are trapped within a besieged city and struggle to survive. Violence here is incredibly dangerous for survival, and should be avoided at all costs.

* Papers please

You play as a border control employee that must validate that all people crossing the border have the correct documentation. Due to the nature of the environment there will be some guns/violence involved, but it is by far not the main focus of the game. Glory to Arstotzka.

These games may not be to your liking, depending on how hard you are on the "NO gun/violence" requirement. These approach the topics from a more civilian view than other games.

Journy does not explicitly tell a story, but it allows you to try to figure it out for yourself.

What is the character? What is it doing? What are those? During gameplay, you might reason to possible answers.