I’ve been working on an app for the last few months - it’s been a wild ride. Learning how to take an army of digital minions and turn out a sophisticated application has been amazing and sometimes frustrating. I’ve learned lots but something recently has really improved my mental experience. “No Jargon. Use Domain appropriate language to describe tasks and work.” Or something similar. I watched a talk - https://www.youtube.com/watch?v=v4F1gFy-hqg While most of that is self evident he mentioned the importance of common vocabulary. I don’t subscribe to cave man mode - I still want to see what’s written. However, on long running tasks I realized a few things. #1 Claude loves Jargon. #2 Jargon is bad. Why? Jargon repurposes a word’s meaning. This is fundamentally a bad thing for an LLM which makes predictions based on the words in the context. If I had more time, I’d love to prove it - but this “drift” (A word Claude is fond of) destroys sessions and work threads, especially longer running tasks. Important words and concepts get distorted by using lazy vocabulary and the the real meaning and intent of the task loses direction. Critical for our own processing - I’ve found myself skipping over words I don’t have a good grounding for in the conversation context. I can tolerate it to a small extent but eventually it’s half jargon and you skip over it. Worse yet - it makes understanding what the LLM is saying very difficult. I’ve found this phenomenon rather pernicious and it creeps into the session rather than clobbering me outright. So - no Jargon. When Claude starts “Minting” certificates, tell it to get back on track. submitted by /u/Nice_Cellist_7595
Originally posted by u/Nice_Cellist_7595 on r/ClaudeCode
