| ▲ | gundugi-man 3 hours ago |
| > The single biggest annoyance with Opus 5 is that it writes too elliptically. This is even more painful for non-native English speakers like myself. I feel fairly comfortable reading academic papers or in general, communicating in professional context. But with Opus 5, it feels like reading a literature book: load-bearing, inert, wholesale, hunk, verbatim, and so on... I can figure out the meaning, but working with CC became unenjoyable. |
|
| ▲ | throwaway_7274 an hour ago | parent | next [-] |
| As a native speaker, it feels like reading an impression of a literature book by a high school English class’s most overconfident student who’s only ever read LinkedIn-speak. Anyway, you might have more luck just writing to it in your native language. It’ll be equally crummy, but maybe you’ll find it easier to decode. |
|
| ▲ | inferniac 2 hours ago | parent | prev | next [-] |
| the tip that was floating around on x was to tell it to use "ASD-STE100 Simplified Technical English" cladue desktop has an instructions sections under general options, you can put something like "try to stick to ASD-STE100 Simplified Technical English, keep answers short and to the point" funnily enough the placeholder they suggest when its empty is "keep answers short and to the point" |
| |
| ▲ | a012 an hour ago | parent | next [-] | | I dont know what ASD-STE100 is before but I use the exact instruction (without the ASD code) to Claude since the very beginning, and with Opus 5 I have to remind it very often to rephrase the documents | |
| ▲ | stefan_ 2 hours ago | parent | prev [-] | | CLAUDE.md is mostly powerless against the reinforcement learned crap. I'm up to three separate instructions telling it to cut out the hyper verbose, retelling history comments and it still writes them every time. | | |
| ▲ | strulovich 2 hours ago | parent | next [-] | | The best trick I have after asking it nicely in all sort of ways is: 1. Have it build a scoring script that penalizes words outside a simple English list and approved jargon. Penalize sentences over 15 words as well. Add whatever else. 2. Run it in a loop to reduce the score while preserving intention This works much better than other ways I’ve tried. Of course it costs more. And I would apply it only to the output to the user, not the thinking process (I think the AI thinks better with their crazy English) Of course, sometimes nuance is lost by this process. That’s just the nature of making things simpler. | |
| ▲ | ValentineC an hour ago | parent | prev | next [-] | | Claude Code has an "output styles" setting that supposedly directly modifies the system prompt: https://code.claude.com/docs/en/output-styles | |
| ▲ | epistasis 2 hours ago | parent | prev | next [-] | | On many sessions I have taken to adding an all caps "ANSWER WITH ONE PARAGRAPH ONLY" scream at the end of all my input. It's the only thing that gets results. | |
| ▲ | 0x500x79 2 hours ago | parent | prev | next [-] | | Yep, it might work for one or two turns but I see it regress pretty quickly with instructions and/or CLAUDE.md. It has to be deeper. | |
| ▲ | smoe an hour ago | parent | prev [-] | | What has worked reasonably well for me so far is not trying to stop it from writing its inane walls of text in the first place. Let it vomit it all out, then have a /tldr with instructions to make the last answer concise and intelligible |
|
|
|
| ▲ | moomin an hour ago | parent | prev | next [-] |
| I'm particularly fond of "load-bearing seam", which it loves to use. It rather hilariously fails the "draw the metaphor" test. |
|
| ▲ | waldarbeiter 2 hours ago | parent | prev | next [-] |
| Thank you, my dict.cc search history contains exactly some of these words. I felt like my english got much worse but when Claude kept talking about "hunk" over and over I felt like the problem is maybe not on my end. |
| |
| ▲ | yorwba 2 hours ago | parent | next [-] | | "hunk" is git terminology. When you use `git add --patch` (which you probably should, if you use `git add` at all) you get prompted "Stage this hunk [y,n,q,a,d,e,?]?" which is self-explanatory (?) and the hunk refers to whatever change git is highlighting at the moment. | | |
| ▲ | Gracana an hour ago | parent | next [-] | | I wondered how far back the usage of that term went. I was familiar with it in patch, so I did a little digging and found it in the v1.3 (1985!) source by Larry Wall: https://groups.google.com/g/mod.sources/c/xSQM63e39YY | |
| ▲ | tempest_ 2 hours ago | parent | prev | next [-] | | "seam" is apparently... according to Claude itself a term from 'Working Effectively with Legacy Code' by Michael Feathers which I have not read. All it took was for one sub agent to use this term and it stated using it everywhere all the time. I have not read the book and prefer other terminology but it only takes 1 sub-agent or 1 usage in the context before it poisons everything else. | | |
| ▲ | sudosteph 40 minutes ago | parent | next [-] | | That's funny. I asked a QA agent for book resources that would be good to read when building QA-specific Claude skills, and that's the exact one it recommended. | |
| ▲ | oooyay an hour ago | parent | prev [-] | | An interface is an example of a seam in regular code. It's basically what forms architectural shapes that you can depend on for both design and testing. | | |
| ▲ | 5 minutes ago | parent | next [-] | | [deleted] | |
| ▲ | chuckadams an hour ago | parent | prev | next [-] | | It's a fairly good concise term ... load-bearing, even. /ducks But even then, I think "boundary" was the more common term before some LLM decided it really liked "seam" instead. | | |
| ▲ | SoftTalker 4 minutes ago | parent [-] | | In architecture, a seam is not load bearing. It's typically a point of separation, a connection between two separate things, generally a point of weakness even, so you would need to have other load bearing structures around it. "Load-bearing seam" doesn't make any sense. |
| |
| ▲ | tempest_ 24 minutes ago | parent | prev [-] | | Yes, and I prefer that term because no one but claude ever talks to me using the word seam every other paragraph. I have instructions which is confidently ignores to never use seam and instead say interface. |
|
| |
| ▲ | waldarbeiter an hour ago | parent | prev [-] | | You're right, hunk is official git wording that I didn't know and I should know since I use --patch flag... It's just that I never heard a human (including online) reason about hunks. While at the same time (from my observation) people say things like code chunk, code snippet etc. a lot. |
| |
| ▲ | VeninVidiaVicii 2 hours ago | parent | prev [-] | | This is the problem with commercial AI and the way our minds work; it writes garbage and we’re trained to think we’re stupid because we can’t understand it. |
|
|
| ▲ | piraccini 2 hours ago | parent | prev | next [-] |
| OK so I am not the only one :D |
|
| ▲ | kypro 2 hours ago | parent | prev [-] |
| It seems to have a preference for speaking in poetic or highly expressively language, rather than precise and concise as most engineers like to talk. The amount of times I have to ask "precisely what do you mean by x?". It's kinda like that engineer that likes to throw around unnecessary technical jargon just to sound more inteligent, worse because at least you could kinda understand what the technical jargon dude was on about even if it was totally unnecessary. |
| |
| ▲ | dofm an hour ago | parent | next [-] | | Claude writes like a guy at a firm I used to work with in the 90s; he was my employer's "visionary"; he'd worked at a whole lot of different companies on both sides of the Atlantic in inexplicably high-placed roles given that he was often bluffing, and was considered a lucky hire of a rising star. He'd be called into meetings with high end clients to spout off. He really needed you to know he understood, but very often he didn't. I think it's likely that LLMs adopt the tone and style of their developers' communication culture. If you assume this is the case, you can infer quite a bit about the differences between OpenAI, Anthropic and Google DeepMind. I am more and more clear about this given the way Muse Glimmer writes. Like a talented, slightly snarky guy who is maybe a bit of a dick but quite fun to be around. | | | |
| ▲ | Planktonne 37 minutes ago | parent | prev | next [-] | | It's not poetic or highly expressive; it's business cruft. | |
| ▲ | Applejinx an hour ago | parent | prev [-] | | I asked some AI-using compatriots a while back who were complaining about this, 'isn't it doubling down on bullshitting you?' and got some pushback along the lines of 'it isn't a person therefore doesn't have dark motives like that therefore can't be doing that to us'. Didn't convince me. I think bullshitting like this can be a behavior, not just the intention of a human. If it's blowing a lot of smoke to use fancy words and phrasings (and semicolons! All the trimmings) it's fair to ask if it's systemically bullshitting you: i.e. the behavior is meant to have you shut up and trust it and not ask questions. Who's driving that is still important: if the company's directing it to do that in system prompts that are adversarial to users, that's a big yikes. If it's an epiphenomenon of the company demanding it get ever smarter, maybe it's a sign that their demands are not having that result, rather they're making it bullshit more explicitly and mimic more 'smart' signifiers. |
|