CV-driven development occurs when technology or architecture choices serve developers’ career interests more than the system’s needs. Learning and staying current are legitimate goals; the risk begins when they become disconnected from organizational economics, ownership, and operational capacity. section 2.2
Test an attractive or expensive proposal by asking:
- What specific risk does the additional cost reduce, and is that risk severe enough to justify it? section 2.2
- What operational burden will the choice add, and who will own it after delivery? section 2.2
- What cheaper option was rejected, and what signal would show that it is no longer sufficient? section 2.2
Figure 2.3 Budget changes the architecture that is realistic.

Use the budget-and-architecture relationship to keep technical ambition aligned with what the organization can sustain. section 2.2
