seneca

Why would it not be legal to enforce a contract after 9 years? If she didn't want it enforced after a duration, she could have negotiated for that, or just not signed it.

I don't see how it's principled to legally swear to not do something, then turn around and do it anyways. She's an adult, she has agency, and she chose to enter that contract.

It's also not like we're talking about a legal whistleblower here. That act DOES (and should) have a lot of legal protections. This is someone writing a book that they personally profit from.

Acknowledging that I'm not adding much to the conversation here, but I just wanted to respond to say you actually changed my opinion with this post. Those examples are slop not because their category is bad, but because most things are slop. That's fairly clearly true once it's pointed out.

> Lying assumes an intent to deceive.

Yeah, fair point. "Misleading" would be a better term, perhaps.

> ... I immediately feel the need to go ask a fresh instance the question and/or another LLM

Not to criticize at all, but it's remarkable that LLMs have already become so embedded that when we get the sense they're lying to us, the instinct is to go ask another LLM and not some more trustworthy source. Just goes to show that convenience reigns supreme, I suppose.

You'll notice I specifically said "victims of their own success". Obviously these problems are induced by the fact that they have so many users. Blowing a lead due to inability to handle the demands of success is still a path to losing the lead.

Oh really? Do they have availability problems too?

They seem to be a victim of their own success. Their response times are quite bad, and it's widely believed they are doing something to degrade service quality (quantizing?) in order to stretch resources. They just announced that they're cutting their usage limits down during peak hours as well.

They're in serious risk of losing their lead with this sort of performance.

> Any massive infra migration is going to cause issues.

What? No, no it's not. The entire discipline of Infrastructure and Systems engineering are dedicated to doing these sorts of things. There are well-worn paths to making stable changes. I've done a dozen massive infrastructure migrations, some at companies bigger than Github, and I've never once come close to this sort of instability.

This is a botched infrastructure migration, onto a frankly inferior platform, not something that just happens to everyone.

I share your concern. Airlines seem to be anticipating this. There was a recent publicized incident of American Airlines removing a woman from a flight for playing audio over her phone speakers. United has similar policies. As I understand it, both are saying they will ban passengers over it.

I'm not sure Microsoft is good at creating technology OR products. Microsoft is good at enterprise sales.

I've tried several of these sorts of things, and I keep coming away with the feeling that they are a lot of ceremony and complication for not much value. I appreciate that people are experimenting with how to work with AI and get actual value, but I think pretty much all of these approaches are adding complexity without much, or often any, gain.

That's not a reason to stop trying. This is the iterative process of figuring out what works.

> But Google actually knows how to do research and how to apply it to products.

I have seen basically no evidence of this. Google knows how to do research to create technology. Google is pretty terrible at creating product though.

Yeah, agreed. Daily isn't really necessary outside of initial launch and maybe a busy season. It's really just often enough to build a good sense of production use, and keep it up to date.

These categories are extremely broad. Top Executive includes general managers, legislators, school superintendents, mayors, city administrators, and a lot of other government jobs. The name is misleading, it's basically non-frontline management.

Chief Executives is actually a specific sub-category of it and is, obviously, much smaller.

I'm not sure if this is what the writer was getting at, but I tend to check telemetry for my production applications regularly not because I'm looking for things that would fire alerts, but to keep a sense of what production looks like. Things like request rate, average latency, top request paths etc. It's not about knowing something is broken, it's about knowing what healthy looks like.

Understanding what your code looks like in production gives you a lot better sense of how to update it, and how to fix it when it does inevitably break. I think having AI checking for you will make this basically impossible, and that probably makes it a pretty bad idea.