rroblak

Yeah, made me chuckle that an LLM— probably Claude— was used to write this.

The use of "regime shift" is what gave it away for me. I've never seen a human write that, but Claude does from time to time.

At least they removed occurrences of "load-bearing".

You should read Postman's Technopoly. He critiques "context-free" news as leading to a confused viewership and argues that it's an unexpected consequence of modern news media: trying to give the viewer a fully-coherent understanding of current news simply wouldn't play as well as shallow, quick stories.

This creates a skewed information-action ratio, where people are inundated with information about problems they have no power to influence. Consequently, news is reduced to a form of trivia, and the act of being "informed" becomes a passive— and ultimately meaningless— ritual.

This. People are getting the message that "sugar is bad" but the public health messaging of "fat is bad" still lingers in many people's heads. It's sad, because as you mentioned some days are indeed essential nutrients. Especially for kids and pregnant women.

The article specifically mentions a previous study that showed that gains from short rests were greater than those from sleep:

> In a previous study, led by former NIH postdoctoral fellow Marlene Bönstrup, M.D., Dr. Cohen’s team showed that most of these gains happened during short rests, and not when the subjects were typing. Moreover, the gains were greater than those made after a night’s sleep and were correlated with a decrease in the size of brain waves, called beta rhythms.

> Allowing any version drift of dependencies at all means that if you don’t check in and restore using the package lock file, you cannot have reproducible builds.

This is the germane point in this incident.

The parent comment mentions that SemVer "guarantee[s] breaking changes are expressed through major versions". This is a common misperception about SemVer. That "guarantee" is purely hypothetical and doesn't apply to the real world where humans make mistakes.

The OP `is-promise` issue is an example of the real world intruding on this guarantee. The maintainers clearly didn't intend to break things but they did because everybody makes mistakes

Which points to the actual value proposition of SemVer: by obeying these rules, consumers of your package will know your _intention_ with a particular changeset. If the actual behavior of that changeset deviates from the SemVer guidelines (e.g. breaking behavior in a patch bump), then it's a bug and should be fixed accordingly.

Back to the parent's point about locking dependency version— I would add that you should also store a copy of your dependencies in a safe location that you control (aka vendoring) if anything serious depends upon your application being continually up and running.

That would make the difference between me using this tool and not using this tool. Losing my shell history isn't worth a momentary ergonomics gain.

Google is, fundamentally, an engineering company. Despite their size and breadth, they still don't understand customer support. Their approach is to use software to solve problems, and they insist on doing so even when it's clear that software isn't up to the task.

Unfortunately, customer support is a hard problem. Despite all of the advances in NLP, I still abhor automated customer support systems when I have a complex issue. Just let me talk to a human.

Google long ago ran the numbers on providing human customer support and realized it's not the sort of ultra-scalable business function that they like to invest in. Rather, they'd like to believe that they can build software systems that don't require human customer support. As an end user, this feels like too much hubris and not enough empathy. It may work from the perspective of a product manager looking at percentages on a dashboard, but it sucks as someone in the real world trying to get something done with one of their products that's not functioning as it should.

I use the full suite of Google Products, including Project/Google Fi. This article describes one of my nightmares— getting locked out of my Google account. I'm fortunate that I have good friends that work at Google that could help out in such a worst-case scenario. This blogger is fortunate, too. Undoubtedly, some Googler will read this post and help them out.

But the average person isn't so lucky. If you're Jane or Joe Schmoe in Middle America, you're going to be screwed when your Google account goes haywire. I've had friends whose Google accounts have gotten into weird states that prevented them from using Google services for no obvious reason. I suspect this is due to an unfortunate consequence of Conway's Law [1] at work in Google's identity implementation.

[1] https://en.wikipedia.org/wiki/Conway%27s_law

One use case is maintaining node-level state for stream processing systems. This gives you a scaleable way to do stateful computations (such as aggregations) without the complexity and performance cost of hitting a remote data store. Such support is built into Samza using RocksDB. [1]

[1] http://samza.apache.org/learn/documentation/latest/container...

CAH would never admit it, but I feel like at least part of this can be seen as political commentary.

From the top of their page: "The holidays are here, and everything in America is going really well" (emphasis mine).

It's hard for me not to read the last part of that as sarcasm, given many people's reaction to the recent US election.

Perhaps CAH is saying that the US is digging itself a hole by electing Trump and a Republican Senate.

Agreed. I was surprised that the article didn't mention the Hawaiian Pidgin expression "da kine"[1], which functions similarly to "jawn". Funnily enough, the da kine Wikipedia page makes the same claim regarding uniqueness of expression.

[1] https://en.m.wikipedia.org/wiki/Da_kine

Actually, it is: http://en.wikipedia.org/wiki/England

One thing to add to this discussion— DFW's description of the Federer/Agassi point in Roger Federer as Religious Experience doesn't actually match up all that well with what actually happened.

See for yourself: https://www.youtube.com/watch?v=jDwG5rJVtdc

And note the discussion in the comments about the video not matching up at all with DFW's description, despite key indicators that it is the point DFW was talking about[1].

[1] Key indicators such as Federer's backsteps and McEnroe's commentary.