tech-debt
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseTech Debt Management
Tech Debt管理
Systematically identify, categorize, and prioritize technical debt.
系统性地识别、分类并确定Tech Debt的优先级。
Categories
分类
| Type | Examples | Risk |
|---|---|---|
| Code debt | Duplicated logic, poor abstractions, magic numbers | Bugs, slow development |
| Architecture debt | Monolith that should be split, wrong data store | Scaling limits |
| Test debt | Low coverage, flaky tests, missing integration tests | Regressions ship |
| Dependency debt | Outdated libraries, unmaintained dependencies | Security vulns |
| Documentation debt | Missing runbooks, outdated READMEs, tribal knowledge | Onboarding pain |
| Infrastructure debt | Manual deploys, no monitoring, no IaC | Incidents, slow recovery |
| 类型 | 示例 | 风险 |
|---|---|---|
| Code debt | 重复逻辑、抽象不足、魔法值 | 漏洞、开发缓慢 |
| Architecture debt | 应拆分的单体应用、错误的数据存储 | 扩展限制 |
| Test debt | 覆盖率低、不稳定测试、缺失集成测试 | 回归问题上线 |
| Dependency debt | 过时库、无人维护的依赖 | 安全漏洞 |
| Documentation debt | 缺失运行手册、过时的README、隐性知识 | 新员工上手困难 |
| Infrastructure debt | 手动部署、无监控、无IaC | 事故、恢复缓慢 |
Prioritization Framework
优先级框架
Score each item on:
- Impact: How much does it slow the team down? (1-5)
- Risk: What happens if we don't fix it? (1-5)
- Effort: How hard is the fix? (1-5, inverted — lower effort = higher priority)
Priority = (Impact + Risk) x (6 - Effort)
为每个条目从以下维度评分：
- 影响：它会在多大程度上拖慢团队进度？（1-5分）
- 风险：如果我们不修复它会发生什么？（1-5分）
- 工作量：修复难度有多大？（1-5分，反向计分——工作量越低，优先级越高）
优先级 = (影响 + 风险) × (6 - 工作量)
Output
输出结果
Produce a prioritized list with estimated effort, business justification for each item, and a phased remediation plan that can be done alongside feature work.
生成一份优先级排序的列表，包含每个条目的预估工作量、业务合理性说明，以及可与功能开发并行执行的分阶段修复计划。