What is the main authority for large C ++ projects?
For years I have re-read John Lakos' classic classic, Large Scale C ++ Software Design . It was not only the first guide of its kind, but also revolutionized how to design a C ++ project in an efficient way to this day!
Do you think his ideas are outdated now? Some of the C ++ techniques in the book are actually old (remember that the book was written before the last standard was published).
What a good authority to guide building a large system in C ++ these days.
Don't get me wrong, I'm not giving up on Lakos at all. It will always refer to me and take the main place on the bookshelf.
thank
source to share
Interestingly, his next book, Scalable C ++: Component-Based Development, is expected in 2006.
I don't think it has ever borne fruit ... one day it will be possible!
In addition, Agile Principles and Patterns are a widely accepted and effective programming paradigm development. I move my gears in these directions.
Check out this book: Agile Software Development, Principles, Patterns, and Practice
source to share
The volume of the book is limited:
- Move implementation data from header and into CPP file
- Avoid circular dependencies.
Despite the fact that these topics are dedicated to these topics, the topics themselves are very narrow.
A lot, and most of them are a "big C ++ project" problem elsewhere ...
- Version control for large teams / many branches
- Planning
- Integration testing
- Defining requirements
- Reliability
- Service
... but these topics are not C ++ - specific.
source to share