Should I design my classes from the outside (interfaces first) or from the inside (data first)?, C++ FAQ

C++ FAQ

From Marshall Cline: Bjarne Stroustrup, Herb Sutter, Andrei Alexandrescu, Pearson / Addison-Wesley Publishers and I collaborated to create a new C++ Super-FAQ! It's a team effort, with huge contributions from each of us and with amazing support from dozens of brilliant editors. The result is "awesomer" than ever! I originally wrote/published the FAQ in 1991 and now look forward to this new phase - and to continue working with it for another 20 years!

On a personal note, I'm at Oculus VR and it is amazing - fabulous people doing fabulous work. We're hiring more fabulous people so write me if that's you!

FAQ: Should I design my classes from the outside (interfaces first) or from the inside (data first)? ←(in the new Super-FAQ)

It's in Section: Operator overloading:

FAQ: What's the deal with operator overloading?
FAQ: What are the benefits of operator overloading?
FAQ: What are some examples of operator overloading?
FAQ: Is operator overloading supposed to make the class' code clearer?
FAQ: What operators can/cannot be overloaded?
FAQ: Overloading operator== to use string comparison?
FAQ: Can I create operator** for to-the-power-of?
FAQ: But which operators should I override?
FAQ: Guidelines / "rules of thumb" for overloading operators?
FAQ: Creating a subscript operator for a Matrix class?
FAQ: Should my Matrix interface look like an array-of-array?
FAQ: Part two of making my Matrix interface look like an array-of-array?
FAQ: Designing classes from the outside-in vs. inside-out? (this FAQ)
FAQ: Overloading prefix/postfix forms of operators ++ and --?
FAQ: Which is more efficient: i++ or ++i?