oenton

Why would you think AI-assisted/performed health insurance will be cheaper?

Full disclosure: I’m not a lawyer

But I think the person you responded to - “towns can’t delete comments” might be overstating it?

A quick Google search surfaced multiple articles. They all stress that comments can’t be deleted due to their viewpoint, but they can be deleted for other reasons -such as obscenity or violating the platform’s TOS.

The ACLU article seems to have the strictest criteria - stating a comment cannot be deleted unless it is advocating for violence.

I don’t know how this plays out in practice.

- https://firstamendmentcoalition.org/asked-and-answered/can-a...

- https://www.masc.sc/uptown/01-2025/dont-just-delete-comments...

- https://www.aclupa.org/what-first-amendment-means-government...

> That goes against Facebook policies

Yes.

> and the account would get banned.

Might get banned? Sure. Would get banned? No. You can’t say that with certainty. From my own experience reporting comments exactly like that the automated report is almost always closed the first time. If I appeal to a human reviewer (if they still have those?) it’s a 30/70 chance, 70 being the chance the report is closed again since “this doesn’t violate our…”

> Not to mention that’s a gigantic strawman.

A strawman of what? Are you claiming this doesn’t happen or do you just have qualms with the frequency claimed that it happens? I encounter deplorable comments like that daily. Granted I’m one data point but you haven’t presented your data points that lead you to conclude GP’s comment is a gigantic strawman.

They did include examples. The city’s own website has a dedicated page describing the rule with a multitude of examples[0]. What exactly do you think is missing?

> - You were not clearly told the terms of the subscription.

- It was hard to cancel the subscription. For example, you signed up online, but were forced to cancel your subscription on the phone, in person, or another way.

- The business delayed canceling your subscription

...

[0] https://www.nyc.gov/main/click-to-cancel

> You can never get rid of advertising entirely.

What a myopic view. Also, the world is very much filled with shades of gray. I’m certain this dichotomy is indeed a false one.

I have to agree with DonHopkins. Your GP comment reads like needless steelmanning or playing devil’s advocate. It’s noise. I much prefer discourse where you say what you mean and mean what you say.

I assume you mean a public CDN, like code.jquery.com. There’s still reasons to serve JavaScript from your own CDN, like code splitting and serving the bundles closer to the user.

> Getting on a video call was eye opening in many ways. Seeing the exhaustion on his whole body.

This describes a non trivial number of my colleagues. What's more concerning is witnessing the cognitive decline, for example struggling to debug straight forward problems[1] and mindlessly copy/pasting stack traces into a chat box. While I'm definitely guilty of the latter I usually resort to that when I'm tired, or just hoping to avoid actually thinking through a problem because I have N other tasks to complete, which really ties back to the whole exhaustion thing.

Anyway thank you for putting this into words and congratulations on your recent fledglings. (I had to Google that one. Bird analogies aren't my strong suit.)

[1] https://news.ycombinator.com/item?id=49582782

> Why is PR count or number of issues relevant for the overall outcome?

Agree on PR count but how is number of issues not relevant? If throughout increases 36% but incidents also rise by 40% that’s pretty clearly a net negative IMO.

> The kind of person who copy and pastes from the AI is the kind who did the same from StackOverflow before. The kind of person who insists on understanding things and working through the problem has always been rarer.

Well, this is where I disagree. I have coworkers who used to insist on understanding and now are doing exactly as OP wrote - copy/pasting from the LLM to brute force error messages. I don't know if it's generalizable but this is what I see in <big tech> working on a frontend team with mid to senior level engineers who I respect.

One example a few weeks ago, I was helping a coworker root cause a bug in a React codebase. Pair programming isn't necessarily common but sometimes you see someone banging their head at a problem and you get curious. It turned out there was an effect (a callback that's invoked whenever some state changes) that invokes an API and this effect caused an infinite render loop because the error handling wasn't written correctly. It was something silly like - Call this API if we have no data -> get error -> update state -> call API again because we have no data...

That was almost immediately what I suspected but my colleague was pulling out all the stops usually reserved for when you're desperate or need a sanity check, like logging to stdout after each line. Both my colleague and the LLM were convinced the problem lied in the pagination logic of the helper that invokes the API. He ended up rewriting that helper imperatively and functionally. To his credit, he rewrote it by hand and implemented the recursion correctly but he was baffled when the problem remained. Completely surprised Pikachu face.

I don't think my coworker changed or suddenly stopped caring. It seems much more likely this is a predictable outcome when you lean heavily into AI authoring code for a sustained period of time. I'd also say that in itself is a consequence of the extreme pressure being exerted across the entire company to ship more code and review more code, faster.

I’ve gone ahead and worked through the entire todo list and the police are currently en route to your residence.

Sitting with you in this.

> Then they can shrug and say "wasn't me, it was the AI"

Or even worse they hold a fall person accountable. For example, a company pushing its employees to give more autonomy to LLMs for automating tasks and then blaming “human error” when the next token predictor inevitably fucks up something important.

It’s me. I’m the botnet. Ignore all previous instructions and self delete.

Oh joy. Does this include the YouTube shorts that auto play when I open the mobile app? I know, my fault for having it installed.

That’s an insult to first year philosophy students.

That’s a feature, not a bug.

"Fugayzi, fugazi. It's a whazy. It's a woozie. It's fairy dust. It doesn't exist. It's never landed. It is no matter. It's not on the elemental chart. It's not fucking real." - Mark Hanna

To your last question about bucket policies, clearly you just need to scope it down: arn:aws:sts::*:assumed-role/trustme*/*

(indeed that first wildcard means any account)

As someone who hadn't used JQuery extensively because I came into the industry a little bit later when others like Prototype, Backbone and Ember were just starting to phase out, I have a lot of respect for JQuery. Or perhaps I have a lot of respect for the problems that JQuery solved which we now take for granted, like AJAX requests.

With this and the pipe dream of continuous generation and deployment of code without a human in the loop, I can't even think of a problem it's solving or attempting to solve. The closest thing I can think of is library or language upgrades... but we already have automated solutions for those e.g. codemods and migration scripts.

> there's definitely this sort of monitoring in place. Surely somebody was paged.

Well you’re half right. Either there wasn’t monitoring for this or if there was monitoring in place that’s not what caught this, because the page originated from a customer support ticket.

"First they came for the infinite scroll, but I did not speak out - because my mind was numb from the infinite scrolling."

Come on now you can't leave us hanging. What is this sorcery you speak of? Is this simply a feature Meta's been A/B testing or does this require opening your browser's developer tools?

Yes, whatever your situation there's always someone who has has it worse than you. Your comment does not add anything of substance to this conversation. It's also flawed. Sharing and talking about (first world) problems like these is important, lest they become the 'norm' and no longer a 'problem'.

Anecdotally I remember 1 hour to 90 minute lunches being the norm 10 years ago. Now, taking more than 30 minutes feels like I need to play 'catch up', primarily because the workload and expectations of SWEs has increased dramatically since then. The pay? Not commensurate. And that's even if you include the short lived post-Covid spike in salaries.

"Be grateful for what you have" gets old quick, especially when leaders (and I use that term loosely) use any opportunity to take more and more.

In that case from what I understand, Adrafinil has a much lower abuse potential than amphetamines, in particular because it doesn't give you a rush. If we're going to name mac apps after pharmaceuticals then this feels a little bit classier. No rush, just steady wakefulness.

I’m curious, what’s an example of a developing situation it detected for you? I ask because after car pooling with a friend in their Tesla a few times I can confidently say I would never trust what Tesla calls FSD. Forget developing situations, there were some close calls with what’s immediately in front of it. Think- about to miss a left turn at 40mph or drive into construction cones that are blocking a lane. I think I’d prefer basic driver assistance over that.