Claude’s blunt engineering feedback shows a real UX problem
Claude was used to check a work-related structural engineering calculation that had not been practiced for years. The problem involved a beam system, and the solution used , where separate simplified cases are solved and then combined.
Claude pointed out errors in the approach and said its earlier answer was more internally consistent because it did not have a “” problem. In math and engineering, can describe a situation where a solution becomes unclear, unstable, or not uniquely defined, but the word can sound cold or insulting to a non-.
Claude later connected this style to technical material such as textbooks, question-and-answer sites, and engineering forums, where words like “degenerate,” “trivial,” and “ill posed” are common when describing mistakes. The useful part was the calculation check; the weak part was the tone.
Key points
- Claude helped review a structural engineering calculation.
- The calculation used , a that combines results from simpler cases.
- The word “” may be technically valid but can feel harsh in normal conversation.
- Claude linked its blunt style to the tone often found in technical writing and engineering forums.
- A practical fix is to tell the what tone and explanation level to use before asking for a review.