"Clearly, I reject the view that there is one way that is right for everyone and for every problem"
About this Quote
Bjarne Stroustrup has long argued that software engineering is about informed tradeoffs, not orthodoxy. The line rejects the comforting idea that there exists a single, universally correct method, language, or pattern that solves all problems for all people. Reality in computing is too varied: domains differ, constraints shift, and priorities collide. What matters is matching tools and techniques to context.
That stance is visible in the design of C++. It is a multiparadigm language, deliberately accommodating object-oriented programming, generic programming, procedural styles, and even functional idioms. It aims for zero-overhead abstractions so you can write high-level code without sacrificing performance when it counts. Templates, RAII, deterministic resource management, and the STL reflect a belief that different problems call for different forms of abstraction and different costs. The language does not force a single worldview; it gives you choices and expects judgment.
Stroustrup’s view also pushes back against cycles of dogma: the insistence that pure OO, pure functional programming, or any one framework is the answer. Each paradigm offers strengths that shine under certain constraints and become liabilities under others. Systems programming with tight latency budgets, large-scale data processing, embedded devices with tiny memory, and GUIs with rapidly changing requirements each reward different tradeoffs in safety, speed, expressiveness, and simplicity.
Pluralism is not license for chaos. With many options comes the responsibility to reason about consequences, measure, and maintain coherence within a codebase. Consistency of style, clarity of interfaces, and shared principles matter precisely because contexts differ. The rejection of a single right way implies humility: let evidence and constraints guide decisions, not ideology.
Beyond programming, the sentiment models an engineer’s mindset. Complex systems rarely yield to universal recipes; they yield to careful analysis, empiricism, and a willingness to adapt. The most reliable path to quality is not the one true way, but the ability to choose a good way for the task and to change course when the task changes.
That stance is visible in the design of C++. It is a multiparadigm language, deliberately accommodating object-oriented programming, generic programming, procedural styles, and even functional idioms. It aims for zero-overhead abstractions so you can write high-level code without sacrificing performance when it counts. Templates, RAII, deterministic resource management, and the STL reflect a belief that different problems call for different forms of abstraction and different costs. The language does not force a single worldview; it gives you choices and expects judgment.
Stroustrup’s view also pushes back against cycles of dogma: the insistence that pure OO, pure functional programming, or any one framework is the answer. Each paradigm offers strengths that shine under certain constraints and become liabilities under others. Systems programming with tight latency budgets, large-scale data processing, embedded devices with tiny memory, and GUIs with rapidly changing requirements each reward different tradeoffs in safety, speed, expressiveness, and simplicity.
Pluralism is not license for chaos. With many options comes the responsibility to reason about consequences, measure, and maintain coherence within a codebase. Consistency of style, clarity of interfaces, and shared principles matter precisely because contexts differ. The rejection of a single right way implies humility: let evidence and constraints guide decisions, not ideology.
Beyond programming, the sentiment models an engineer’s mindset. Complex systems rarely yield to universal recipes; they yield to careful analysis, empiricism, and a willingness to adapt. The most reliable path to quality is not the one true way, but the ability to choose a good way for the task and to change course when the task changes.
Quote Details
| Topic | Wisdom |
|---|
More Quotes by Bjarne
Add to List
