Assertion Quote by Alexander Stepanov
“Complexity assertions have to be part of the interface”
About This Quote
Source Article: “Designing Generic Algorithms”, 1997
Interfaces should explicitly include complexity requirements to set correct expectations.
In simple terms: Complexity must be part of interface design.
Key Takeaway
Specify algorithmic costs clearly.
Themes
software design
complexity
API
software engineering
Mood
analytical
practical
Type
technical
educational
When to use this quote
- Library design
- API documentation
- performance testing
- client communication
Key Concepts
Big‑O notation
interface contracts
Questions to Reflect On
- How do you balance abstraction with performance details?
- When should complexity be hidden?
A Different Perspective
Complexity may be hidden or variable in practice.
![“Object-oriented programming aficionados think that everything is an object… this [isn't] so. There are things that are objects. Things that have state and change their state are objects. And then there are things that are not objects. A binary search is not an object. It is an algorithm” quote by Alexander Stepanov](https://sms4smile.com/quotes/img-quotes/ef9/alexander-stepanov-55292_algorithms_object-oriented-programming-aficionados_89704.jpg)
