Ignoring what "legally" forced entails, and just focusing on the mechanics of renaming stuff: Even if your code base can be updated with a simple "s/old/new/" regex (and, IME, this never, ever works as well as you thought it would, and always creates a long tail of manual grepping and editing), you still have to fix the docs, deal with breaking API changes, support multiple versions, provide upgrade paths, deal with confused users, etc. etc. etc.

And, um, confusingly, the examples you cite are actually even more complicated and work-intensive than what is being talked about in this article, because they also require URL / domain name updates, legal document changes, regulatory filings, etc. etc.

TLDR: the contention that "name changes happen easily" is not an accurate description of the situations you are citing.

Although tbf I kind of doubt if this was ever really the case - probably this is imagined nostalgia for idealized bygone times. And given that this is a strategy that requires, y'know, long-term investment and planning, it's not like it's going to start happening anytime in the near future

But if you're making a big fundamental change to a system, I do know that it shouldn't start with a single "+279,276 -4,272" PR. It starts with a small patch with the core of the change so that everyone can understand what it does and how it works. (I mean, ideally, a change like this starts with documentation, discussion, diagrams, surveys of existing implementations, etc, before you start writing code)

You don't cram everything into a single 270K line PR, even (especially) with an LLM, unless you specifically don't want anyone else to look too closely at what you did.

I'm sorry, what? What exactly do you think is happening here?

Nope! That is - training on lowest-common-denominator, low-signal high-noise "idiotspeak" was not at all inadvertent.

The attacker here was trying to use a software agent to run DOS attacks. Perhaps they were a "naive noob outsider", perhaps they misconfigured something. It is not generally the victim's responsibility to try to figure this out.

And it is definitely not the victim's responsibility to determine the attacker's state of mind if they don't even have any way to contact them. In this case, the attacker was using their software agent specifically to avoid interacting with the targets of their attack.

the good news is I've seen at least two seemingly irredeemable assholes grow out of it when they realized it wasn't working. but in general I don't think introspection and self-examination are universal traits

I just ran the upgrade to 6.0.0, and it downloaded so many things concurrently that it killed my wifi (old router). Is there a way to cap bandwidth or maximum concurrent connections? (this is something I have to do in many download heavy apps, e.g., steam)

Running anything at constant 100% utilization means you are going to be working in crisis mode all of the time. Even in factory labor, the Toyota Way is several decades old now, and it involves making sure everyone has at least a little breathing room to step back and think about what they're doing. And obviously this is even more important for "knowledge workers" or anyone whose output requires any amount of creativity.

High functioning organizations have a good (not too much, but not too little) amount of slack in their work pipelines. Pretty sure there is not a single person with an MBA (or, lol, any consultants) that knows this anymore.

Comments URL: https://news.ycombinator.com/item?id=48485160

Points: 47

# Comments: 16

> To help identify accounts and actions that have been directly verified by me, I will use the term “NATCIOS” to indicate anything I have personally verified.

Does anyone have any idea what "NATCIOS" means here? I cannot find this term anywhere on the internet. (Honestly, that sentence is really weird. I almost wonder whether this is someone experiencing a health episode?)

[1] https://lwn.net/ml/all/AS8PR08MB6055AE3054B34F6A567AC95BCF08...

The legal profession uses the term "reckless disregard", see, e.g., [1].

[1] https://en.wikipedia.org/wiki/New_York_Times_Co._v._Sullivan