| ▲ | PatronBernard a day ago | |
Claude Code's creative use of language in an engineering context is often quite infuriating. I want language to be as simple as possible, it should be accessible and require as little context as possible. Below are a few examples that Code wrote that I encountered in my own work (related to signal processing): "excursion" (means: a spike/jump — a value that rises or deviates from baseline, just say spike or outlier) "legitimate majority-normal baseline" (means: a real majority of normal pixels) "matched pool of pure-noise ('normal') pixels" (means: the same number of normal pixels, don't bring pools into this) "ablation" (means: comparing before vs. after — turning a thing on/off to see what changes) I actually used Claude Code to try and find examples like these but not entirely unexpectedly it had a very hard time detecting these, even though I encounter them like every other sentence. I can imagine this style is great when writing prose, not so much when writing documentation. Similarly, I tried using Claude Design to make some slides, and the individual slides were fine, but just about every other slide it used different words to denote the same concept, which I would say is the fastest way to lose your audience. | ||