5 ms·
> This is the same shape as many other life-cycle bugs [...] Claude-ism detected. IME with Claude Code an object does not have a type or definition, apparently
by alexjplant 3mo ago
> This is the same shape as many other life-cycle bugs [...]
Claude-ism detected. IME with Claude Code an object does not have a type or definition, apparently, but rather a shape (or at least it reaches for that word before more technically-accurate ones). Problems are not of a similar class or type, but of the same shape. Functions are not defined by their signatures but by their shape. Who talks like this and how did it make its way into the training data so pervasively?
- dang 3mo agoI think you're probably right that the article was AI-assisted, but (if so) it's important not to confuse that with the thing the article is about. Google wouldn't pay $90k for a hallucination. I don't mean that as a criticism—the question of how to receive AI-processed content is chaotic right now. I'm working on a post about that here: https://news.ycombinator.com/item?id=48887149 https://news.ycombinator.com/item?id=48887149. Btw, Nebula Sec is a YC startup in the current batch. We've been working with them on how to launch on HN, and one of the things I've been trying to explain is that the HN audience won't respond well to LLM-generated reports. The underlying work, though, is impressive. These guys know what they're doing—the OP is by no means their only significant find—and the fact that they're doing it with an agent, rather than the traditional way, is significant.
- cwillu 3mo agoA thing that notably triggers my allergies is that if significant human effort went into something, a few paragraphs written by a human seems like a trivial additional investment; if that last touch is missing, it's really hard for me to extend the benefit of the doubt that there really is something there. Obviously this is only one signal among many, one that can be overruled, but the ick remains regardless.
- dang 3mo agoI agree to an extent, but there are many exceptions, so one can't really withhold the benefit of the doubt. For example, non-native English speakers (as is the case with these guys IIRC) frequently use these tools. Maybe they shouldn't—as I've been telling a lot of people who email, mistakes are rapidly becoming a sign of authenticity at this point—but the belief that they need to is widespread, and this doesn't mean they didn't do significant work. (Side note: it's a common assumption that machine-translated text is in a different category from LLM-edited text. From what we're seeing, that assumption is unfortunately wrong.) Another important case is people with disabilities who find these technologies assistive. Again, one can argue that they're increasingly better off just posting their own writing in the raw, but this is a pretty obscure point to get across to people, and in some cases it would impose a significant burden. Beyond those cases, a lot of people just don't write easily, and/or don't feel their writing is any good. A lot of them are using LLMs to compensate for that, and this by no means implies that their work is bad. Maybe they just have a phobia about writing and/or don't express themselves well that way. People who enjoy writing or are confident writers fail to understand how emotionally fraught writing is for many others. Personally I'm down with the "writing is thinking" view, from which it follows that bad writing is bad thinking. But it doesn't follow that "thinking is writing" - that's a much stronger claim, from which it would follow that good thinking is good writing—and this I think is false.
- sph 3mo agoNon-native speakers have learned and improved their English for decades by trial-and-error, let’s stop using that as an excuse to use LLMs. I have been there, and making mistakes is how one learns to communicate effectively in another language. If one doesn’t put effort in their writing, I am not going to put effort to read whatever slop they put out instead. Simple as that.
- dang 3mo agoWhat you say implies that people should "learn and improve their English" before posting their work to HN. I'm not with you on that, and here's why: we're trying to optimize for the most-intellectually-interesting site, not the most-English site: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sort=byDate&type=comment&query=curiosity%20optimiz%20by:dang https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor..., even though people do have to post in English here. That may sound like too fine a distinction, but it isn't. Here's an example: Show HN: Getting GLM 5.2 running on my slow computer - https://news.ycombinator.com/item?id=48842459 https://news.ycombinator.com/item?id=48842459, which was the #1 thread on HN a couple days ago (https://news.ycombinator.com/front?day=2026-07-09 https://news.ycombinator.com/front?day=2026-07-09). That user is a non-native English speaker who helped get his posts into a format that HN could appreciate. His work is obviously excellent—the community response was unambiguous. But I don't think it would have made it through without our help. I'm sure you weren't saying that if someone can't describe their work in good English then it must be slop, but the space is larger than you make it sound. Which is unfortunate in a way—it would be easier to narrow it down, but then we'd miss posts like that one.
- cwillu 3mo agoPie-in-the-sky synthesis: translation is easy these days, so maybe non-english writers can and should just write in their own native language and let the readers provide their own translation. Perhaps English no longer needs to be the lingua anglais of western tech writing :p
- deleted 3mo ago[deleted]
- clhodapp 3mo agoIt frankly doesn't matter how much human effort went into finding the vulnerability, it just matters if it exists, how severe it is, and how easy it is to exploit.
- titularcomment 3mo agoIf an exploit is actually working, human effort is void and the ML has done a great job. However most of the time its hallucinating, confidently talking gibberish in technical lingo. This phenomena is only amplified by those who try to make a quick buck without effort using older models, not reviewing output or prompting properly ('find me bugs in Linux, make no mistakes')
- etenal 3mo agoThere is no if, it works, people have video proof, google confirmed, Linux patched and fixed. And you still believe this is AI gibberish
- a_t48 3mo agoYou should put a note in Find a Cofounder not to do that as well. Huge turnoff for me, though I guess a great filter.
- dmittman 3mo agoIsn't this just observation bias? "If I haven't encountered something, then it must not be real?" (Paraphrasing)
- alexjplant 3mo agoI must confess that I asked a leading question. At no point did I say that the usage wasn't real; by way of dramatic omission I was more pointing to the fact that a common ECMAScript/React-ism is overrepresented in Claude's training set to the point that it's being applied to situations not involving duck-typed languages. I'm not a grammatical prescriptivist but I find it viscerally troubling that a bunch of LLM cargo-culted terms are starting to inform how we talk about our work.
- etenal 3mo agoWe apologize for the confusion. We used AI to run final grammar pass and didn't noticed it changed some wording (shape is one of them). Will be more careful in the future
- TurdF3rguson 3mo agoExcept that working with Claude has me saying things like shape lately. I think I like it.
- not-a-llm 3mo agotalking about data and function shapes is quite common in functional programming world https://blog.jle.im/entry/functors-to-monads-a-story-of-shapes.html#a-story-of-shapes https://blog.jle.im/entry/functors-to-monads-a-story-of-shap...
- sethammons 3mo agoWhen working in Elixir, everything is about the shape of things. I have now taken that word usage from that ecosystem because I find it useful.
- marginalia_nu 3mo agoNo this is normal programming terminology. Here I am using 'shape' in this sense back in 2021: https://www.marginalia.nu/log/40-wasted-resources/ https://www.marginalia.nu/log/40-wasted-resources/ and even more similar usage again in 2023 'the shape of the algorithm' (which was post-claude I guess, but this was before I even tested any LLM): https://www.marginalia.nu/log/87_absurd_success/ https://www.marginalia.nu/log/87_absurd_success/
- treyd 3mo agoI've used phrasing like this from time to time before, like when trying to compare two ideas that are unalike but have some fuzzy similarities. I wouldn't use it to describe functions but "problems", "solutions", and other fuzzy things.