kaizen

原文涵盖的主题

• Kaizen: Continuous Improvement
• Overview
• When to Use
• The Four Pillars
• 1. Continuous Improvement (Kaizen)
• Principles
• In Practice
• 4. Just-In-Time (JIT)

Small improvements, continuously. Error-proof by design. Follow what works. Build only what's needed. Core principle: Many small improvements beat one big change. Prevent errors at design time, not with fixes. Always applied for: Code implementation and refactoring Architecture and design decisions Process and workflow improvements Error handling and validation Philosophy: Quality through incremental progress and prevention, not perfection through massive effort. Small, frequent improvements compound into major gains. Incremental over revolutionary: Make smallest viable change that improves quality One improvement at a time Verify each change before next Build momentum through small wins Always leave code better: Fix small issues as you encounter them Refactor while you work (within scope) Update outdated comments Remove dead code when you see it Iterative refinement: First version: make it work Second pass: make it clear Third pass: make it efficient Don't try all three at once Documents why, when, and how Before adding new patterns: Search codebase for similar problems solved Check CLAUDE.md for project conventions Discuss with team if breaking from pattern Update docs when intro

这里只展示节选，请以完整原文和当前要求为准。