Recommend me a book...

H

HDS

Expert Member
Joined
Mar 3, 2013
Messages
1,849
Reaction score
2
...on advanced c++. I have worked through 2 cpp books (covering basic + some advanced material) and a Qt book for gui programming. I didn't like it though, the deviation from generic cpp.

So yeah, recommend me a book on advanced c++ concepts and I will get it. Or even a link to learning material that you trust.
 
Get the grand daddy of all programming books: Design Patterns by GoF (Gang of Four). Not C++ per se, but very useful in its own right and often associated with advanced C++ programming. The code snippets were either in C or C++ - can't remember all that well.
 
Thanks for the suggestions. I think the Design Patterns by GoF is what I'm looking for.

@Mike thanks for the offer, but I'm about 9000 kilometres away from you :D.
 
Pho3nix said:
Heard 5differant senior dev's recommend this book.
The other 5 recommended this : http://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215
Click to expand...

Well, it IS a very useful book. :) I can't imagine a life without software patterns, my code would be a jumbled mess. DDD is very useful in its own right, but as soon as you start working with highly customizable, complex systems with dynamic data structures, the DDD principals fall a bit flat. DTOs and SOA offer a far more scalable and reusable platform by rather putting the business logic in services and keeping objects clean.

Don't get me wrong, I've always been a huge proponent of DDD and apply the principals in building "engines", but the end-users of my "engines" (our dev team) just use the SOA architecture that the engines expose and use the domain objects primarily as DTOs.
 
FarligOpptreden said:
Well, it IS a very useful book. :) I can't imagine a life without software patterns, my code would be a jumbled mess. DDD is very useful in its own right, but as soon as you start working with highly customizable, complex systems with dynamic data structures, the DDD principals fall a bit flat. DTOs and SOA offer a far more scalable and reusable platform by rather putting the business logic in services and keeping objects clean.

Don't get me wrong, I've always been a huge proponent of DDD and apply the principals in building "engines", but the end-users of my "engines" (our dev team) just use the SOA architecture that the engines expose and use the domain objects primarily as DTOs.
Click to expand...

Thanks for the feedback. Ordered a copy.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X