docs: add Lehman classification as LLM failure mode#21
Conversation
Extends the 'LLM-specific failure modes' section with Lehman's S/P/E classification and the Laws of Software Evolution. E-type systems (embedded in the world, must evolve) suffer from accelerated Lehman decay when LLM-generated, because LLMs have no persistent memory of project history. Closes LLM-Coding#19 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThe change adds documentation about Lehman's software classification and laws of software evolution to the i18n file, specifically updating the "LLM-Specific Failure Modes" section in both German and English locales. A new bullet point addressing "Accelerated Lehman Decay" is introduced, explaining how AI-generated code may accelerate quality decline in E-type systems due to lack of persistent project-history memory. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
- picomatch: method injection + ReDoS - vite: path traversal in optimized deps, arbitrary file read via WS - yaml: stack overflow via deeply nested collections Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/i18n.js`:
- Around line 307-308: Update the Lehman terminology capitalization in the
translation strings: change "*S-Type*", "*P-Type*", "*E-Type*" to "*S-type*",
"*P-type*", "*E-type*" and change "*Continuing Change*", "*Increasing
Complexity*", "*Declining Quality*" to lowercase "*continuing change*",
"*increasing complexity*", "*declining quality*" so German and English variants
use the same lowercase convention; locate and edit the German string starting
with "Beschleunigter Lehman-Decay" and the corresponding English translation
entries in the i18n strings (the Lehman-law sentence blocks) to make these
replacements consistently.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| *Beschleunigter Lehman-Decay* — https://en.wikipedia.org/wiki/Lehman%27s_laws_of_software_evolution[Lehmans Gesetze (1980)] unterscheiden *S-Type* (formal spezifiziert, geschlossen), *P-Type* (Problemlösung mit Näherungs-Spec) und *E-Type* (in die Welt eingebettet, muss mitevolvieren — Banking, SaaS, Agenten). E-Type-Systeme unterliegen *Continuing Change*, *Increasing Complexity* und *Declining Quality*. AI-generierter Code beschleunigt diese Zerfallsdynamik, weil LLMs kein persistentes Gedächtnis der Projekthistorie haben — sie können nicht "mit dem Code altern". Bei S-Type-Code (Algorithmen, reine Utility-Funktionen) ist das Risiko gering. Faustregel: Je E-typischer das System, desto mehr Review-Budget und Refactoring-Kapazität einplanen.`, | ||
| }, |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify if German Wikipedia page exists for Lehman's laws
echo "Checking if German Wikipedia article exists for Lehman's laws..."
curl -s -o /dev/null -w "%{http_code}" "https://de.wikipedia.org/wiki/Lehmans_Gesetze_der_Softwareentwicklung"
echo ""
curl -s -o /dev/null -w "%{http_code}" "https://de.wikipedia.org/wiki/Lehman-Gesetze"
echo ""
echo "Checking English Wikipedia article (currently linked)..."
curl -s -o /dev/null -w "%{http_code}" "https://en.wikipedia.org/wiki/Lehman%27s_laws_of_software_evolution"Repository: LLM-Coding/vibe-coding-risk-radar
Length of output: 210
🏁 Script executed:
#!/bin/bash
# Check the actual content at lines 307-308 and 671-672 in src/i18n.js
echo "=== German version (lines 307-308) ==="
sed -n '305,310p' src/i18n.js
echo ""
echo "=== English version (lines 671-672) ==="
sed -n '669,674p' src/i18n.jsRepository: LLM-Coding/vibe-coding-risk-radar
Length of output: 2408
Fix capitalization inconsistencies between German and English versions
The German and English translations use inconsistent capitalization for Lehman's law terminology:
-
Type terminology: German uses "S-Type", "P-Type", "E-Type" (uppercase 'T') while English uses "S-type", "P-type", "E-type" (lowercase 't').
-
Law names: German uses "Continuing Change", "Increasing Complexity", "Declining Quality" (title case) while English uses "continuing change", "increasing complexity", "declining quality" (lowercase).
Align both versions to lowercase convention ("S-type", "continuing change", etc.) to match standard software engineering literature and Lehman's original terminology.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/i18n.js` around lines 307 - 308, Update the Lehman terminology
capitalization in the translation strings: change "*S-Type*", "*P-Type*",
"*E-Type*" to "*S-type*", "*P-type*", "*E-type*" and change "*Continuing
Change*", "*Increasing Complexity*", "*Declining Quality*" to lowercase
"*continuing change*", "*increasing complexity*", "*declining quality*" so
German and English variants use the same lowercase convention; locate and edit
the German string starting with "Beschleunigter Lehman-Decay" and the
corresponding English translation entries in the i18n strings (the Lehman-law
sentence blocks) to make these replacements consistently.
2 participants
Summary
Test plan
npm run build) ✅Closes #19
🤖 Generated with Claude Code
Summary by CodeRabbit