HN user

Seattle3503

2,283 karma
Posts3
Comments741
View on HN

You are talking about false negatives, but this thread started with a discussion around the potential for false positives causing writers anxiety

Even if 2/10000 is true that’s nowhere near accurate enough to make aggressive accusations that create anxiety at levels people need to medicate with potentially fatal consequences.

False positives and false negatives are different problems that have different impacts.

Does your single example prove that Pangram doesn't work, or that it doesn't work on short snippets of text? Try to get a detection error on a longer run of text. I'd be curious to see the results, particularly if you can get a false positive.

Pangram’s market claims are very different from independent validations of the platform.

Do you have a link to independent validations? The ones I found, like an upcoming nber paper confirm the companies claims.

Presumably the people paying the author for translation services are aware of AI, but for whatever reason are choosing a humans services instead. IMO it would be a form fraud to heavily rely on AI and not disclose that to the customer.

My team has been using AI to add code, but also to aggressively remove old deprecated code. "Is anyone still using this? How does this get called" is easier to answer when you can toss your FE, BE, and entire codebase at an agent and let it create a map of your software project. IDEs can do this in a single language to some degree usually in a single project, but RPC, REST, etc... break some of these tools in a lot of IDEs.

The burden of proof should fall on the platform, not the victim. The question is not whether a harmed user can show specific damage. The question is whether the company can show, before rolling a product out to billions of people, that it is not predatory by design.

That's asking every company to prove a negative before rolling out new features.

Could we have a regulatory agency that keeps an eye on dark patterns and deals with them as evidence emerges that something is harmful.

If I need to grab 100 locks, they are all moving around a lot, but I've got the first 10, will the order be the same for someome trying to get the same 100? Eg maybe someone swaps two that neither of us has grabbed yet.

I'm hopeful that improvements in LLMs mean we can ditch ORMs (under the guise that they are quicker to write queries and the inbetween mapping code with) and instead make good use of SQL to harness the powers that modern databases provide.

Maybe we can ditch active models like those we see in sqlalchemy, but the typed query builders that come with ORMs are going to become more important, not less. Leveraging the compiler to catch bad queries is a huge win.