5 ms·

Ive given up trying to fight claudes language, and Im afraid Im getting used to it and can even understand what claude is saying faster or should I say I can pa

Ive given up trying to fight claudes language, and Im afraid Im getting used to it and can even understand what claude is saying faster or should I say I can parse it faster now.

miranaproarrow 24d ago
gate= some sort of a guard or test name= a variable name or fields load bearing= coupled dependencies that can break other things if you change it
- ricardobeat 24d ago
  [dead]
- alex43578 24d ago
  While these are clunky, was this phraseology that much of a problem for people? I don't like reading it, but I didn't find that I couldn't read it.
  - hombre_fatal 24d ago
    But slowing down to decipher text instead of single pass simple reading is the problem. Random example from a session I have open: > *One new failure mode the doubling opens, and how it is closed.* A ring never shrinks. With two 8-byte index words per record instead of one, the ring's doubling comes inside the budget's reach in the blank regime: a doubling taken [...] It takes extra deciphering cycles to see "the doubling", "budget's reach", "the blank regime", etc. and figure out what it's referring to. I had to read that opening sentence multiple times. At first I parsed it like "One cat the table yawns". Sometimes it's so encumbered I can't tell what it's saying at the directional level: good or bad, fast or slow? "Your blank regime negated the pre-armed run's dilemma but clawed back the overall metrics." It's not how I'd phrase things if I were trying to be easily understood, though Claudese is probably great for LLMs due to ad hoc jargon usage.
    - alex43578 24d ago
      Oh yeah, those examples are gibberish. Mine hasn't been that bad. More like the comment I responded to, where it's just being a bit clunky. Your examples read like Claude's gone a bit schizo.
  - PunchyHamster 24d ago
    just seeing it too often I'd imagine. I don't really mind it
  - SkyPuncher 24d ago
    I get tripped up on the intensity of its us and the ambiguity it tends to apply them with. Minor inconvenience != load bearing, yet Claude consistently uses it while missing actual loading bearing things. Likewise, it tends to jump to terminology that’s technically correct but practically meaningless.
- knollimar 24d ago
  Load bearing irks me having a construction background. Claude will often comment on it using the phrase wrong when it gets context.
- thih9 24d ago
  invariant = constant you were right to push back = previous response was wrong
- StilesCrisis 24d ago
  pinned = forced in some way tree is green = tests built and ran without error landed = surprisingly, not "made a commit" but rather "finished the code." It might be confused because we're using Perforce and not git.

Ive given up trying to fight claudes language, and Im afraid Im getting used to it and can even understand what claude is saying faster or should I say I can parse it faster now.

miranaproarrow 24d ago

gate= some sort of a guard or test name= a variable name or fields load bearing= coupled dependencies that can break other things if you change it

ricardobeat 24d ago
[dead]
alex43578 24d ago
While these are clunky, was this phraseology that much of a problem for people? I don't like reading it, but I didn't find that I couldn't read it.
- hombre_fatal 24d ago
  But slowing down to decipher text instead of single pass simple reading is the problem. Random example from a session I have open: > *One new failure mode the doubling opens, and how it is closed.* A ring never shrinks. With two 8-byte index words per record instead of one, the ring's doubling comes inside the budget's reach in the blank regime: a doubling taken [...] It takes extra deciphering cycles to see "the doubling", "budget's reach", "the blank regime", etc. and figure out what it's referring to. I had to read that opening sentence multiple times. At first I parsed it like "One cat the table yawns". Sometimes it's so encumbered I can't tell what it's saying at the directional level: good or bad, fast or slow? "Your blank regime negated the pre-armed run's dilemma but clawed back the overall metrics." It's not how I'd phrase things if I were trying to be easily understood, though Claudese is probably great for LLMs due to ad hoc jargon usage.
  - alex43578 24d ago
    Oh yeah, those examples are gibberish. Mine hasn't been that bad. More like the comment I responded to, where it's just being a bit clunky. Your examples read like Claude's gone a bit schizo.
- PunchyHamster 24d ago
  just seeing it too often I'd imagine. I don't really mind it
- SkyPuncher 24d ago
  I get tripped up on the intensity of its us and the ambiguity it tends to apply them with. Minor inconvenience != load bearing, yet Claude consistently uses it while missing actual loading bearing things. Likewise, it tends to jump to terminology that’s technically correct but practically meaningless.
knollimar 24d ago
Load bearing irks me having a construction background. Claude will often comment on it using the phrase wrong when it gets context.
thih9 24d ago
invariant = constant you were right to push back = previous response was wrong
StilesCrisis 24d ago
pinned = forced in some way tree is green = tests built and ran without error landed = surprisingly, not "made a commit" but rather "finished the code." It might be confused because we're using Perforce and not git.