Optimism is an occupational hazard of programming. Feedback is the treatment. — Kent Beck

Optimism is an occupational hazard of programming. Feedback is the treatment.

Author: Kent Beck

Insight: There's something quietly honest about this quote, because it identifies optimism not as a virtue but as an occupational disease—something that comes naturally with the territory. Programmers by nature imagine systems working perfectly, bugs vanishing, code flowing cleanly. That's partly what draws people to the work. But left unchecked, this optimism becomes dangerous. You ship untested features. You underestimate timelines. You assume your elegant solution will actually scale. The flip side is equally important: feedback isn't something to resent or defend against. It's medicine. It's the reality check that stops you from drifting further into an imagined world where your code is flawless and your estimates are accurate. Feedback—from tests, from users, from teammates, from actual production—pulls you back to earth. What makes this insight stick is how universal it really is. You don't need to write code to feel this. Anyone who creates anything encounters the gap between their vision and reality. The writer thinks their draft is better than it is. The manager thinks the plan is foolproof. The trap is mistaking optimism for vision. The antidote is the same every time: genuine, consistent feedback from the outside world telling you what's actually true.

Source: Extreme Programming Explained: Embrace Change, page 12, 1999