taftster

Crazy amounts of language on this video. Not sure if that's even a data point any more.

The two takeaways from me are that:

1. AI allows you to ask stupid questions or the same question without (typically) ridiculing or demeaning you for doing so.

2. Context changes as time rolls by. A question that was asked some period ago might just need to be re-asked, continuously and ongoing.

Now, SO had already suffered its demise prior to AI. But good riddance, from my point of view. StackOverflow was great in its day, essential even. But it fell victim to its own success, I guess.

Right, there are advantages of your defect list riding right along with the code repository itself. The history here is more interesting and keeping it connected to git allows portability options (maybe across network divides).

Your response here regarding CRDT was enlightening and thought provoking to me. Thank you. Really appreciate the distinction of "intent" especially in the context of human social interactions vs. code precision. Very interesting and insightful.

It's an unfortunate statement. And it does feel like it discredits you and the heroic efforts of those like you.

But this is probably forgiven as just sensationalism in writing, which is all too common. Not to excuse the author, but these types of writeups tend to drift into name calling and finger pointing a little too soon.

"Shamefully" is definitely the wrong word here, for sure.

I'd love to play a game that uses these as building blocks. Is there anything that approaches it?

Interesting. I thought it was because the river emptied into the Gulf closest to the state of Mississippi. Like, it would have been slightly unintuitive to have named it the Missouri River all the way down past those Gulf Coast states. The history of river names and deciding which name continues after a confluence is quite interesting.

I was noticing that when I grab and spin the globe, most of the river systems shown on the map disappear (as do the wind flow indicators). But a few major river systems still remain on the map.

In the United States, I thought it was interesting that the Missouri River (which starts in Three Forks, Montana) was chosen as that river. I assume the choice was because this is the longest river, but maybe not quite as well known as the Mississippi river perhaps. And I would guess that not everyone knows the Missouri starts in Montana.

When you let go of the grab, other rivers are redrawn. For the US, that includes the major river systems (including the other major contributors to the Mississippi), which makes sense.

Interesting visualization is all.

This is probably true. Today. But I think we're finding the problems LLMs are solving to be both paradoxically predictable but surprising at the same time. Not saying you're wrong, but scheduling and bin-packing seem like cards that will eventually fall to a bespoke prompt.

I mean, "breaks down" is different from "scheduled maintenance". Most definitely the later can be scheduled during less busy hours.

Yes, it's definitely more likely for an individual already in an upper floor to return to ground than a stop above or below. The people queuing up in simulations don't seemingly get this right all the time.

Also the group of people going to or returning from lunch is real as well. The grouping factor happens more at the middle of the day and less at the morning or evening. Primarily because of lunch.

In these various elevator algorithms, it's not commonly discussed the overall wear and tear on the elevator. More movements would typically translate to faster repair times. Hydraulic fluids needing to be replaced, parts breaking, etc.

Efficient elevator algorithms will often suggest moving an elevator into a preempted positioning strategy, based on time of day or peer elevator positions. The scheduler might move an elevator up to offset one coming down, for example. The demand-signal algorithms at least minimize movement in this way.

I think minimizing maintenance at the cost of increasing wait times is probably an important balance to get right. No doubt, the cost owners for maintenance are not going to perceive the wait time of passengers to be as important.

Could you put that in units of HP Printers and Toner please?

Easy for you to say, assuming your PC is clean. I don't think negligent is the right word though. Ignorant maybe? Or some form of naivety? The negligence might be on software or hardware vendors, but grandma isn't to blame for the problem.

I'd suggest just ensuring that the entire rules of chess are first evaluated or supported in a chess program, before worrying about ELO rating, etc.