Science Quote by Wietse Venema

Software bloat rarely arrives as a villain; it shows up wearing a lab coat and carrying “just one more feature.” Wietse Venema’s line slices through that comforting myth. “Adding functionality” sounds like a simple accretion story: more code, more capability, progress. Venema insists the opposite. Functionality is not a pile of lines; it’s a reshaping of a system’s behavior, risk profile, and social contract with its users.

The intent is corrective, almost disciplinary. As a security-minded scientist (and the kind of builder who treats real-world failure as data, not drama), Venema points at the invisible costs engineers love to externalize: complexity, attack surface, maintenance burden, performance regressions, and the subtle ways new features invalidate old assumptions. Adding code is measurable. Adding functionality is epistemic: you’re changing what you can know about the system, what you can prove, what you can test, and what you can confidently promise.

The subtext is a critique of naive engineering economics. Teams often budget for implementation and forget integration: documentation, observability, backward compatibility, threat modeling, user support, and the long tail of debugging. The quote also nudges at organizational incentives: feature shipping is rewarded; restraint is rarely celebrated. Venema’s phrasing is deliberately plain, which makes it sting more. It’s not poetic; it’s a lab note. That’s why it works.

Contextually, it reads like a message forged in the security world, where every “small change” is a new opportunity for misconfiguration, unexpected interactions, and exploitation. Functionality isn’t additive; it’s entangling.